Re: [squid-users] Squid specific site failures

On Thu, 26 Jan 2006, Mark Elsen wrote:

> The remote webserver is broken, it sends http1.1 replies on http1.0
> requests :

HTTP/1.1 servers MUST respond with HTTP/1.1, even if the request was
HTTP/1.0. But at the same time it MUST NOT use any HTTP/1.1 features not
compatible with HTTP/1.0 i such responses..

> http://web-sniffer.net/?url=http%3A%2F%2Fwww.baylor.edu%2F&submit=Submit&http=1.0h&gzip=yes&type=GET&ua=Mozilla%2F5.0+%28Windows%3B+U%3B+Windows+NT+5.1%3B+nl%3B+rv%3A1.8%29+Gecko%2F20051111+Firefox%2F1.5+Web-Sniffer%2F1.0.23

The error on this web site is not detected by web-sniffer. But it is
reported in cache.log:

2006/02/11 15:24:26| WARNING: unparseable HTTP header field
{Content-type=text/html; charset=iso-8859-1}
2006/02/11 15:24:26| in {Connection: close
Date: Sat, 11 Feb 2006 14:24:26 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Content-type: text/html
X-Powered-By: PHP/5.0.3
Content-type=text/html; charset=iso-8859-1
Content-Length: 19784
etag: "aff9a4b39c43b6c7a59c4e9092662873"
Last-Modified: Wed, 08 Feb 2006 10:34:51 GMT
}

> Advice : - install the latest STABLE release, much code has been added
> to deal with weirdo remote webserver, and provide some sane
> handling for various cases.

Indeed. Current Squid version by default only complains in cache.log about
this server error, without giving an error to the end-user.

Regards
Henrik
Received on Sat Feb 11 2006 - 07:28:08 MST