[Varnish] #908: beresp.cacheable doesn't consider HTTP status 307 to be cacheable

Varnish varnish-bugs at varnish-cache.org
Wed Apr 27 08:15:13 CEST 2011

#908: beresp.cacheable doesn't consider HTTP status 307 to be cacheable
 Reporter:  thiagocsf      |        Type:  defect  
   Status:  new            |    Priority:  normal  
Milestone:                 |   Component:  varnishd
  Version:  2.1.5          |    Severity:  normal  
 Keywords:  cacheable 307  |  
 Varnish variable beresp.cacheable doesn't consider 307 responses to be
 cacheable.  This is by design and documented:


 However, RFC 2616 does state that such requests are cacheable:


 (..) "This response is only cacheable if indicated by a Cache-Control or
 Expires header field."


 Live example available below.
 $ curl  -I
 HTTP/1.1 307 Temporary Redirect
 Cache-Control: public, max-age=600
 Location: http://static.westfield.com/img_resized/retailer/logos/default-
 Status: 307
 Content-Type: text/html; charset=utf-8
 Server: Apache
 Content-Length: 151
 Date: Wed, 27 Apr 2011 06:12:15 GMT
 Age: 0
 Via: 1.1 varnish
 Connection: keep-alive

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

More information about the varnish-bugs mailing list