The response headers has both a content length and a transferencoding set. The spec says that the transfer encoding takes precident over content length, but I would view the presence of both as a bug. I would start looking at the code path from sun one server to squid/varnish as tomcat talking ajp does not introduce either header by default.
Cheers Dace On Tuesday, June 29, 2010, Poul-Henning Kamp <[email protected]> wrote: > In message <[email protected]>, > Davi > d Brown writes: > >>When we put Varnish 2.1.2 in place of Squid we see hex characters showing up >>in content from Tomcat, typically "1ff8". > > This is what is called "HTTP/1.1 chunked encoding" headers. > > Somehow one end does not realize that chunked encoding is being used. > > Check Transfer-Encoding headers and HTTP version fields are not > disturbed. > > > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > [email protected] | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > > _______________________________________________ > varnish-dev mailing list > [email protected] > http://lists.varnish-cache.org/mailman/listinfo/varnish-dev > _______________________________________________ varnish-dev mailing list [email protected] http://lists.varnish-cache.org/mailman/listinfo/varnish-dev
