Varnish showing hex characters from Jakarta-Tomcat connector protocol

David Brown captkiddo at
Wed Jun 30 15:08:16 CEST 2010

You were right, it was wrong. The change I made to the VCL fixed the one
problem but screwed up the rest of the site so I had to back it out.

Attached is a varnish log of the activity. I have some tcpdumps at various
points too if you need them.

I still think it's connected to tomcat and specifically the JK connector. It
seems the JK connector has an 8K limit (AJP 1.3) and breaks up large files
in the transmission between tomcat and the webserver. The characters may be
(?) part of JK's breakup of the file. My reasoning is because I can take the
same file and place it directly on the web server and no problem, only when
it comes from tomcat/jk do we have these issues. ( I can't convince the
programmers to take static content out of their java apps and put it on the
server )

On Tue, Jun 29, 2010 at 5:22 PM, Poul-Henning Kamp <phk at>wrote:

> In message <AANLkTikRDbvceKr14-PKP8RuIC9Djyab0kLiehPG2Ea4 at>,
> Davi
> d Brown writes:
> >I checked and it seems the Transfer-Encoding header is being stripped by
> >Varnish. I can see it when I go directly to the web server but not when I
> >view the file through Varnish.
> >
> >I worked around the problem by adding this to my VCL
> That sounds positively wrong.
> Is it possible that you can capture a varnishlog of one of these
> transaction and send to me ?
> --
> Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
> phk at FreeBSD.ORG         | TCP/IP since RFC 956
> FreeBSD committer       | BSD since 4.3-tahoe
> Never attribute to malice what can adequately be explained by incompetence.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: varnish.log
Type: application/octet-stream
Size: 90564 bytes
Desc: not available
URL: <>

More information about the varnish-dev mailing list