0: 'http://image.link.ru/img/linkru2.gif'
2005/04/13 22:41:33| WARNING: unparseable HTTP header field {HTTP/1.0 200 OK}
2005/04/13 22:41:33| in {Server: .
Content-type: image/gif
Date: Wed, 13 Apr 2005 20:42:55 GMT
Last-modified: Fri, 19 Mar 2004 18:23:56 GMT
Accept-Ranges: bytes
Connection
?
121 |ctx: enter level 0:
'http://link.link.ru/show?squareid=7182&showtype=1&cat_id=110090&tar_id=1&sc=3&bg=FF&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 fi
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
On Tue, 12 Apr 2005 12:04:54 +0200 (CEST)
Henrik Nordstrom <[EMAIL PROTECTED]> wrote:
On Tue, 12 Apr 2005, Evgeny Kotsuba wrote:
Has this [strange] message in log any reasonable information ?
WARNING: unparseable HTTP header field {HTTP/1.0 200 OK}
squid 2.5.x
This is commonly see
On Tue, 12 Apr 2005, Evgeny Kotsuba wrote:
Has this [strange] message in log any reasonable information ?
WARNING: unparseable HTTP header field {HTTP/1.0 200 OK}
squid 2.5.x
This is commonly seen from broken web servers sending two status lines,
presumably caused by a bad CGI or similar
Hi,
Has this [strange] message in log any reasonable information ?
WARNING: unparseable HTTP header field {HTTP/1.0 200 OK}
squid 2.5.x
SY,
Evgeny Kotsuba
