[Varnish] #747: 302 is unconditionally cached by default

Varnish varnish-bugs at varnish-cache.org
Wed Aug 4 18:47:59 CEST 2010

#747: 302 is unconditionally cached by default
 Reporter:  trombik   |       Owner:  phk  
     Type:  defect    |      Status:  new  
 Priority:  normal    |   Milestone:       
Component:  varnishd  |     Version:  2.1.2
 Severity:  normal    |    Keywords:       
 rfc2616 states that "A response received with any other status code (e.g.
 status codes 302 and 307) MUST NOT be returned in a reply to a subsequent
 request unless there are cache-control directives or another header(s)
 that explicitly allow it"

 however, bin/varnishd/cache_center.c caches 302 response without such
 headers. an example is:

 Date:Wed, 04 Aug 2010 10:10:08 GMT
 Keep-Alive:timeout=5, max=50

 the commit log in question simply says "handle 302 for now".


Ticket URL: <http://www.varnish-cache.org/ticket/747>
Varnish <http://varnish-cache.org/>
The Varnish HTTP Accelerator

More information about the varnish-bugs mailing list