Amos Jeffries wrote:
I'm working through a problem where pages from a broken web server
aren't making it through Squid 3.0 (tested up through STABLE 8). The
page source according to the browser (Firefox 2, Firefox 3, or IE7) is
the "28B" which should be the start of the chunk, followed by the chunk
itself, and then "0" that would finish the chunked transfer.
I'm hoping that I can manage to contact the admins of the web server and
get them to fix their problem, but is there any way I can work around
the problem in Squid?
Squid 3.0 does not support chunks. There is a config workaround to drop
the Accept-Encoding header on requests going to known broken HTTP/1.1
servers which try to send chunks to 1.0 clients.
http://squidproxy.wordpress.com/2008/04/29/chunked-decoding/
If you really need chunked and 3.x you will need the HEAD code.
Amos
Thanks, Amos. How is the stability of the HEAD code, and is 3.1 nearing release?
Guy
--
Guy Helmer, Ph.D.
Chief System Architect
Palisade Systems, Inc.
