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

On Wed, 13 Apr 2005 01:24:01 +0200 (CEST)
  Henrik Nordstrom <hno@squid-cache.org> wrote:
> 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.
>
I.E. things like below are now normal ?

121 |ctx: enter level 0:
'http://link.link.ru/show?squareid=7182&showtype=1&cat_id=110090&tar_id=1&sc=3&bg=FFFFFF&bc=FFFFFF&tc=D5EFFF'
122|WARNING: unparseable HTTP header field {HTTP/1.0 200 OK}
123|ctx: exit level 0
124|WARNING: unparseable HTTP header field {HTTP/1.0 200 OK}
125 2005/04/12 15:55:44|ctx: enter level 0:
'http://image.link.ru/img/adhere.gif'
126|WARNING: unparseable HTTP header field {HTTP/1.0 200 OK}
127|ctx: exit level 0
128|WARNING: unparseable HTTP header field {HTTP/1.0 200 OK}
129|ctx: enter level 0: 'http://image.link.ru/pic/1326-4.gif'
130|WARNING: unparseable HTTP header field {HTTP/1.0 200 OK}
131|ctx: exit level 0
132|WARNING: unparseable HTTP header field {HTTP/1.0 200 OK}

> Regards
> Henrik

SY,
Evgeny Kotsuba
Received on Wed Apr 13 2005 - 11:54:53 MDT