[Varnish] #529: Not RFC compliant - headers wiped on 304

Varnish varnish-bugs at projects.linpro.no
Wed Jul 8 13:44:44 CEST 2009

#529: Not RFC compliant - headers wiped on 304
 Reporter:  are    |        Type:  defect
   Status:  new    |    Priority:  high  
Milestone:         |   Component:  build 
  Version:  trunk  |    Severity:  normal
 Keywords:         |  
 Missing http headers when returning a 304-code.

 According to RFC 2616, pt 10.3.5:
 "The response MUST include the following header fields:"
 "ETag and/or Content-Location, if the header would have been sent
 in a 200 response to the same request"

 The http headers are wiped then creating a 304, including etag.

 Our current problem is that we set Cache-Control with max-age, public,
 post-check and pre-check, all to make IE happy, but when the client
 refreshes the page and get a 304 the cache-control is missing and that
 makes IE forget the original caching orders.

Ticket URL: <http://varnish.projects.linpro.no/ticket/529>
Varnish <http://varnish.projects.linpro.no/>
The Varnish HTTP Accelerator

More information about the varnish-bugs mailing list