[Varnish] #1339: vcl_fetch : configuration order

[Varnish]

#1339: vcl_fetch : configuration order
-------------------------------------+----------------------
 Reporter:  flafolie                 |       Owner:
     Type:  defect                   |      Status:  closed
 Priority:  normal                   |   Milestone:
Component:  build                    |     Version:  3.0.3
 Severity:  normal                   |  Resolution:  invalid
 Keywords:  beresp.ttl hit_for_pass  |
-------------------------------------+----------------------
Changes (by scoof):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 This is not actionable as a bug. Please seek help on the mailing lists or
 forum to figure out if this really is a bug.

 I'd say it's most likely a case of misuse of hit_for_pass, and that you're
 serializing the requests for the uncacheable content. By returning
 hit_for_pass with beresp.ttl set to <=0s, you're not saving that you don't
 wish to cache this object, thereby creating a queue for the object.

 Please get back to us, if you have more information, such as logs that
 show that this is really a bug.

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