[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:  closed
 Priority:  normal        |   Milestone:  Varnish 4.0 release
Component:  varnishd      |     Version:  4.0.0
 Severity:  critical      |  Resolution:  fixed
 Keywords:                |
--------------------------+----------------------------------

Comment (by Martin Blix Grydeland <martin@…>):

 In [535d44b8909ee88e8700a35bed79f9ca77e445a4]:
 {{{
 #!CommitTicketReference repository=""
 revision="535d44b8909ee88e8700a35bed79f9ca77e445a4"
 Don't needlessly throw away Content-Length from backend, but assume
 it is sane and pass it to streaming clients, provided we don't munge
 the body along the way.

 The ungzip'ed length stored as attribute has not been backported to
 4.0, meaning on-the-fly ungzip will be delivered chunked.

 Fixes: #1506

 Conflicts:
         bin/varnishd/cache/cache_fetch.c
 }}}

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