[Varnish] #1506: Make better use of Content-Length information: Avoid chunked responses, more control over Range handling

[Varnish]

#1506: Make better use of Content-Length information: Avoid chunked responses,
more control over Range handling
--------------------------+----------------------------------
 Reporter:  DonMacAskill  |       Owner:  phk
     Type:  defect        |      Status:  reopened
 Priority:  normal        |   Milestone:  Varnish 4.0 release
Component:  varnishd      |     Version:  4.0.0
 Severity:  critical      |  Resolution:
 Keywords:                |
--------------------------+----------------------------------

Comment (by valdemon):

 Hi,

 although it's a different use case, it seems to be related to the ticket
 subject. I'm getting the 'Transfer-encoding: chunked' in a case of '204 No
 Content' response, which is wrong by definition.
 I guess this could be easily fixed by extending the 'if' statement in
 following line:
 https://github.com/varnish/Varnish-
 Cache/blob/master/bin/varnishd/http1/cache_http1_deliver.c#L92

 to:
 {{{
 #!c
 } else if (http_IsStatus(req->resp, 304) || http_IsStatus(req->resp, 204))
 {
 }}}

 Checked with the latest 4.0.3.

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