[Varnish] #1027: signal 6 on calling error in vcl_deliver

Varnish varnish-bugs at varnish-cache.org
Mon Oct 17 14:43:18 CEST 2011


#1027: signal 6 on calling error in vcl_deliver
-------------------+--------------------------------------------------------
 Reporter:  kwy    |        Type:  defect  
   Status:  new    |    Priority:  normal  
Milestone:         |   Component:  varnishd
  Version:  trunk  |    Severity:  normal  
 Keywords:         |  
-------------------+--------------------------------------------------------

Comment(by kristian):

 Test case:

 {{{

 varnishtest "Test if you can error in vcl_deliver"

 server s1 {
         rxreq
         txresp -status 200

         rxreq
         txresp -status 200
 } -start

 varnish v1 -vcl+backend {
         sub vcl_deliver {
                 error 201 "ok";
         }
 } -start

 client c1 {
         txreq -req GET
         rxresp
         expect resp.status == 201

 } -run
 }}}

 Comment:

 So, hmm, there are two parts to this. One is that VCC and Varnish disagree
 on where error is allowed (i.e: It should either work or give a VCL
 compile error). The second part is that we don't have error in deliver....
 Pretty sure we had it a short while ago.

 Ah, yes, here we go.

 714e0ef684edef8a370c10676e00fe8411894b91

 https://www.varnish-
 cache.org/trac/changeset/714e0ef684edef8a370c10676e00fe8411894b91

 So that explains why you can't do it.

 I'm removing this from the list of allowed VCL returns in deliver now, and
 that turns this into a feature request of sorts. Though considering we had
 error in vcl_deliver in the past, it might pass as a regression?

-- 
Ticket URL: <https://www.varnish-cache.org/trac/ticket/1027#comment:2>
Varnish <https://varnish-cache.org/>
The Varnish HTTP Accelerator




More information about the varnish-bugs mailing list