Re: unparseable HTTP header field {HTTP/1.0 200 OK}

On Wed, 13 Apr 2005, Evgeny Kotsuba wrote:

> Well, but there is no any key what server and what is bad in {HTTP/1.0 200
> OK} in warning message

Example reply headers where this message is seen:

   HTTP/1.1 200 OK
   Server: sometthing
   HTTP/1.0 200 OK
   Content-type: text/html
   other headers...

> I see it but this {HTTP/1.0 200 OK} in user's log from
> Squid-2.5.STABLE9-Last made me crazy again ;-)

cache.log shold have the offending URL just above this.

Regards
Henrik
Received on Tue Apr 12 2005 - 17:24:03 MDT