On 12/07/2012 7:38 p.m., a bv wrote:
Impossible keep-alive header
http://www.squid-cache.org/Doc/config/detect_broken_pconn/
The server has sent a header telling Squid to keep-alive the connection,
but then has sent an unknown-length response that requires a connection
close.
Amos
]
Subject: RE: [squid-users] Impossible keep-alive header
Date: Mon, 19 Jan 2004 18:48:29 +0100 (CET)
On Mon, 19 Jan 2004, Mike Mitchell wrote:
I've just installed the squid-2.5.STABLE4-20040119 snapshot and now I'm
flooded with Impossible keep-alive header messages.
I have a parent proxy of a Trend
On Fri, 23 Jan 2004, M J wrote:
I had the same problem using the following snapshot
squid-2.5.STABLE4-20040123.tar.bz2.
Henrik wasn4t the keep-alive.patch incorporeted in to the daily snapshot ?
Many thanks in advance, Leon.
All the changes discussed are in the current snapshot.
Please
Sorry Henrik, I use one old topic that had the same problem / configuration
as I do, but I now a realize that there is a lot of them, I m sorry. I ll
give details. I was having a problem that the file cache.log was full of
these warnings
2004/01/23 19:38:38| ctx: exit level 0
2004/01/23
: Wednesday, January 14, 2004 1:51 PM
To: Steve Snyder; Alex Sharaz
Cc: [EMAIL PROTECTED]
Subject: Re: [squid-users] Impossible keep-alive header
On Wed, 14 Jan 2004, Henrik Nordstrom wrote:
Thinking... OK, I think I know what the bug is in that patch.
Confirmed. The logics on what keep-alive
On Mon, 19 Jan 2004, Mike Mitchell wrote:
I've just installed the squid-2.5.STABLE4-20040119 snapshot and now I'm flooded with
Impossible keep-alive header messages.
I have a parent proxy of a Trend Micro Interscan Viruswall version 3.8 running on
the same machine. Here's an example from
On Mon, 19 Jan 2004, Mike Mitchell wrote:
I've just installed the squid-2.5.STABLE4-20040119 snapshot and now I'm flooded with
Impossible keep-alive header messages.
I have a parent proxy of a Trend Micro Interscan Viruswall version 3.8 running on
the same machine. Here's an example from
On Mon, 19 Jan 2004, M J wrote:
Hi Henrik, many thanks for your patch.
Now using squid-2.5.STABLE4-20040119.tar.bz2 with your keep-alive.patch and
no more Impossible keep-alive header messages. Many thanks for your replay!!
;)
Tomorrow this patch will be incorporated in to daily snapshot ?
Yup just downloaded the latest 2.5S4 snapshot and installed it on one of my
caches and they started. All the other caches are o.k.
alex
--On 14 January 2004 10:37 -0500 Steve Snyder [EMAIL PROTECTED]
wrote:
I'm suddenly getting a lot of these errors. Here's an example:
2004/01/14 10:29:35|
On Wed, 14 Jan 2004, Steve Snyder wrote:
I'm suddenly getting a lot of these errors. Here's an example:
2004/01/14 10:29:35| ctx: exit level 0
2004/01/14 10:29:35| ctx: enter level 0:
'http://www.squid-cache.org/Versions/v2/2.5/bugs/'
2004/01/14 10:29:35| httpProcessReplyHeader:
Thinking... OK, I think I know what the bug is in that patch.
What does access.log say?
Regards
Henrik
On Wed, 14 Jan 2004, Alex Sharaz wrote:
Yup just downloaded the latest 2.5S4 snapshot and installed it on one of my
caches and they started. All the other caches are o.k.
alex
--On 14
On Wed, 14 Jan 2004, Henrik Nordstrom wrote:
Thinking... OK, I think I know what the bug is in that patch.
Confirmed. The logics on what keep-alive headers are impossible was a
little too broad, sometimes triggering on fully valid HTTP/1.0 replies.
The patch has been corrected, and attached
12 matches
Mail list logo