[Varnish] #205: Better Vary handling

[Varnish]

#205: Better Vary handling
---------------------------+------------------------------------------------
 Reporter:  des            |        Owner:  des  
     Type:  enhancement    |       Status:  new  
 Priority:  normal         |    Milestone:       
Component:  documentation  |      Version:  trunk
 Severity:  normal         |   Resolution:       
 Keywords:                 |  
---------------------------+------------------------------------------------
Changes (by phk):

  * owner:  phk => des
  * component:  varnishd => documentation

Comment:

 I would read such backend behaviour to be in non-compliance with RFC2616.

 You are right that this can be done in VCL, so I don't think there is any
 benefit from doing anything about it in the varnish source code.

 This is probably something that belongs in documentation/FAQ more than
 anything else.

 Notice that an easier way to do this might be to construct the missing
 Vary: header in vcl_fetch, provided that you know what your backend does
 Vary on.

-- 
Ticket URL: <http://varnish.projects.linpro.no/ticket/205#comment:1>
Varnish <http://varnish.projects.linpro.no/>
The Varnish HTTP Accelerator