[squid-users] Re: Problem with unparseable HTTP header field

On Fri, 18 Feb 2005, Ralf Hildebrandt wrote:

> When I surf to http://www.abstractserver.de/da2005/avi/e/Abs_revi.htm
> and enter any number/character and click "Submit my query", I get an
> error page ("Invalid Response" The HTTP Response message received from
> the contacted server could not be understood or was otherwise
> malformed.
See bug 1242
http://www.squid-cache.org/bugs/show_bug.cgi?id=1242
The issue is that with 2.5S8 (or well patched 2.5S7) squid has become less
tolerant of illegal behaviour from web servers in the headers they serve
before the contents of the web page. If you fetch that page by hand (eg.
with wget -S) you can see the HTTP headers
 1 HTTP/1.0 200 OK
 2 Server: Microsoft-IIS/3.0
 3 Date: Fri, 18 Feb 2005 19:54:50 GMT
 4 HTTP/1.1 200 OK
 5 content-type: text/html
 6 content-length: 2617
 7 Connection: Keep-Alive
which is difficult to make sense of if you actually try to understand it;
is the answer HTTP/1.1 or HTTP/1.0?

        Michael Young
Received on Fri Feb 18 2005 - 13:15:25 MST