On Wed, 13 Apr 2005, Evgeny Kotsuba wrote:
I.E. things like below are now normal ?
As I said this is a quite broken web server, and if you set relaxed_header_parser to "warn" (or off) then more detailed diagnostics of the problem is shown:
2005/04/13 22:41:33| ctx: enter level 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: close HTTP/1.0 200 OK 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: close Content-length: 831 } 2005/04/13 22:41:33| ctx: exit level 0
2005/04/13 22:44:17| 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' 2005/04/13 22:44:17| WARNING: unparseable HTTP header field {HTTP/1.0 200 OK} 2005/04/13 22:44:17| in {Server: . Content-type: text/html Date: Wed, 13 Apr 2005 20:45:40 GMT Last-modified: Mon, 15 Dec 2003 08:26:43 GMT Accept-Ranges: bytes Connection: close HTTP/1.0 200 OK Server: . Content-type: text/html Date: Wed, 13 Apr 2005 20:45:40 GMT Last-modified: Mon, 15 Dec 2003 08:26:43 GMT Accept-Ranges: bytes Connection: close Expires: Wed, 13 Apr 2005 20:45:40 GMT Cache-Control: no-cache Pragma: no-cache Expires: Wed, 13 Apr 2005 20:45:40 GMT Cache-Control: no-cache Pragma: no-cache } 2005/04/13 22:44:17| ctx: exit level 0
Ofcourse it can be debated if it's intentional that the "WARNING: unparseable HTTP header field {HTTP/1.0 200 OK}" is logged in cache.log at debug level 1 when "relaxed_header_parser on" is used (the default). But I think so as the bad line within the header can not be forwarded by Squid and has never been. Earlier versions silently dropped the unparseable line without notice (logged at debug level 2).
Regards Henrik
