Re: [squid-users] invalid HTTP header

On Thu, 17 Feb 2005, [iso-8859-1] Johan Henæs wrote:

> I have upgraded an old squid-proxy to version (Squid Cache: Version 2.5.STABLE7) running Fedora Core 3 (rpms) I have also tried to install "Squid Cache: Version 3.0-PRE3-20050213"..
> Using the squid-servar as a www accelerator, accessing a web-server I get an "invalid request" error message in my browser, together with these lines in the logs :
> ---
> 2005/02/17 11:58:58| ctx: enter level 1: 'http://visualiser.xxxx.no/cgi-bin/login.exe'
> 2005/02/17 11:58:58| WARNING: ignoring unparseable HTTP header field near 'HTTP/1.0 200 Ok'
> 2005/02/17 11:58:58| WARNING: found whitespace in HTTP header {<meta http-equiv="Expires" content="Tue, 10 Oct 1994 14}
> ---

Please try with 2.5.STABLE8.

The patches to 2.5.STABLE7 has been refined many times, and many other
bugs was corrected before 2.5.STABLE8 which could have caused this kind of
problems.

> Browsing through the archives I found a similar problem in msg25634.
> Henrik explains :
> --
> The "200 Ok" line is not a valid HTTP header. Most likely a confused CGI
> script trying to set the HTTP status wrongly.

Your problem looks very different from that discussion.

> Is it possible to solve this problem using the 3.0-release, as I need
> the 3.0 release for reverse proxying a MS OWA- server as well (need the
> "front-end-https" setting)

The Squid-3 tree is not yet up to date with all these changes, and is
known to have several rather major bugs causing malformed
requests/responses.

Regards
Henrik
Received on Sat Feb 19 2005 - 07:57:49 MST