El 20/08/2008, a las 4:24, Amos Jeffries escribió:
Pedro Mansito Pérez wrote:
El 15/08/2008, a las 8:41, Amos Jeffries escribió:
Pedro Mansito Pérez wrote:
Hello,
Our Company is using Squid 2.6.STABLE14 on a Slackware 12.0 box.
A few weeks ago we began to have errors accessing some web pages,
but not all, on a supplier web site. If we do not use a proxy
server we can access those web pages; we have tested it with
Safari, Camino and Firefox on Mac OS X, and IE 6 and 7, and
Firefox on Windows. On Squid 2.6 we get a Zero Sized Reply error;
on a Squid 3.0.STABLE7 test box (also on Slackware 12.0) we have
an Invalid Response Error. If, on Internet Explorer, we disable
the use of HTTP/1.1 on proxy connections we can access the page
using Squid.
The supplier insists that since we can access the pages without
Squid, the problem must be ours. I replied him that it all begin
a few weeks ago, so the problem is theirs.
It's a problem with the Source web server.
The Server is sending FORBIDDEN chunked-encoded data to a HTTP/1.0
client (Squid).
http://squidproxy.wordpress.com/2008/04/29/chunked-decoding/
Hello Amos,
I am not sure that is the problem. I think that the problem is
that, when the client asks for the use of HTTP/1.1, Squid
identifies itself as 1.1 compliant:
Ah, for squid 2.6 to be doing that it has to be patched to do so.
Such broken behavior is exactly why squid other than 2.7 are not
released with that ability.
I still think its the chunk issue, as most in-use squid pass through
a version of Accept-Encoding that triggers the bug in some HTTP/1.1
servers.
[...]
Try the Accept-Encoding config hack and see if its lets you turn on
HTTP/1.1 support in clients again.
Amos,
It fails on: 2.6 STABLE14, 2.7 STABLE4 and 3.0 STABLE7 (with and
without the Accept-Encoding hack). By the way, http://squidproxy.wordpress.com/2008/04/29/chunked-decoding/
mentions that
"This is currently only an issue in Squid 2.5 or earlier and 3.0,
which is still highly modeled around 2.5."
----
