[Varnish] #1797: Content-Type/Content-Length should miss on 304 requests

Varnish varnish-bugs at varnish-cache.org
Fri Jan 8 17:25:53 CET 2016

#1797: Content-Type/Content-Length should miss on 304 requests
 Reporter:  shakalandy  |       Owner:  fgsch
     Type:  defect      |      Status:  closed
 Priority:  normal      |   Milestone:
Component:  varnishd    |     Version:  4.0.3
 Severity:  normal      |  Resolution:  invalid
 Keywords:              |
Changes (by fgsch):

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


 I've had some long thought about this.

 The Content-Length part is already done in 4.1, minus the zero Content-
 Length case.
 The latter is fixed in master.

 Specific headers aside, as the text from RFC7232 4.1 states, the goal here
 is to minimize information transfer.  I don't see how this could affect
 upstream caches and/or force unnecessary revalidations.  It's also worth
 noting that while perhaps not ideal, it's not prohibited (SHOULD NOT as
 opposed to MUST NOT).

 As such I feel this falls into the feature request category. A better
 place to raise this would be:


 If you are adamant on this point, you can always unset the headers in VCL.

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

More information about the varnish-bugs mailing list