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

2005-04-13 Thread Henrik Nordstrom
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://imag

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

2005-04-13 Thread Evgeny Kotsuba
On Wed, 13 Apr 2005 01:24:01 +0200 (CEST) Henrik Nordstrom <[EMAIL PROTECTED]> 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 O

Re: how to apply epoll-2_5 patch to squid2.5-stable9 (fwd)

2005-04-13 Thread Henrik Nordstrom
-- Forwarded message -- Date: Wed, 13 Apr 2005 12:15:40 +0200 From: "[Windows-1250] Paweł Staszewski" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED], squid-users@squid-cache.org Subject: Re: Odp: Re: [squid-users] how to apply epoll-2_5 patch to squid2.5-stable9 Ok :) Some comparisi

Re: Odp: Re: [squid-users] how to apply epoll-2_5 patch to squid2.5-stable9

2005-04-13 Thread Henrik Nordstrom
On Wed, 13 Apr 2005, [Windows-1250] Paweł Staszewski wrote: When i apply epool-2_5.patch In my syslog i have this messages: Apr 13 09:42:25 w3cache1 squid[24895]: commSetSelect: epoll_ctl(EPOLL_CTL_DEL): failed on fd=197: (2) No such file or directory Apr 13 09:42:25 w3cache1 squid[24895]: commSet