[Varnish] #1321: Varnish 3.0.4 sends broken Content-length header

Varnish varnish-bugs at varnish-cache.org
Sun Jun 23 16:01:58 CEST 2013

#1321: Varnish 3.0.4 sends broken Content-length header
 Reporter:  crashev  |       Type:  defect
   Status:  new      |   Priority:  highest
Milestone:           |  Component:  build
  Version:  3.0.4    |   Severity:  normal
 Keywords:           |
 I just upgraded varnish from 3.0.3 to 3.0.4 and it went crazy.
 For some reason varnish 3.0.4 sends broke Content-length hedaer, which is
 empty to backend - in case of using Nginx, Nginx will return error 400 Bad
 Request for it and will report "client sent invalid "Content-Length"

 When debugging with varnishlog -b -m ....
 I saw that it happends always for the second time - when BackendReuse was
 in play, and the header looked like:

 26 TxHeader     b                  Content-Length:

 It is a major flow which crashes apps.

 Sorry don't have more logs, but I found it on production and had to as
 fast as possible have to switch back to varnish 3.0.3 in order to keep
 business running.

Ticket URL: <https://www.varnish-cache.org/trac/ticket/1321>
Varnish <https://varnish-cache.org/>
The Varnish HTTP Accelerator

More information about the varnish-bugs mailing list