[Varnish] #447: ESI chunked output fails if included content served via HTTP/1.0
Varnish
varnish-bugs at projects.linpro.no
Sun Feb 15 19:01:08 CET 2009
#447: ESI chunked output fails if included content served via HTTP/1.0
----------------------+-----------------------------------------------------
Reporter: jayk | Owner: phk
Type: defect | Status: new
Priority: normal | Milestone:
Component: varnishd | Version: trunk
Severity: normal | Keywords:
----------------------+-----------------------------------------------------
Not sure if this is considered a bug or if it's known.
When varnish is talking to a HTTP/1.0 web server, and using ESI, the
chunked Transfer-Encoding used by the ESI engine does not work.
This seems to be because when processing ESI - varnish keeps the HTTP/1.0
of the original response, but tries to use Transfer-Encoding which is an
HTTP/1.1 feature.
Many browsers can cope with this (Command line tools such as curl, wget,
LWPs GET) Webkit based browsers also cope with it. But Firefox and
Internet Explorer obey the HTTP spec and ignore the chunked encoding.
This results in the hex content-lengths for each chunk being displayed in
the browser.
Please feel free to contact me if you need any more information.
--
Ticket URL: <http://varnish.projects.linpro.no/ticket/447>
Varnish <http://varnish.projects.linpro.no/>
The Varnish HTTP Accelerator
More information about the varnish-bugs
mailing list