Re: [squid-users] Impossible keep-alive header
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
RE: [squid-users] Impossible keep-alive header
I had the same problem using the following snapshot squid-2.5.STABLE4-20040123.tar.bz2. Henrik wasn´t the keep-alive.patch incorporeted in to the daily snapshot ? Many thanks in advance, Leon. From: Henrik Nordstrom [EMAIL PROTECTED] To: Mike Mitchell [EMAIL PROTECTED] CC: [EMAIL PROTECTED] 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 Micro Interscan Viruswall version 3.8 running on the same machine. Here's an example from the cache.log file: 2004/01/19 10:58:34| httpProcessReplyHeader: Impossible keep-alive header from 'http://wisapidata.weatherbug.com/WxAlertIsapi/WxAlertIsapi.cgi?GetAlert30Magic=1ZipCode=27519StationID=RALGHUnits=0RegNum=27560925Version=5.02t=1074526042lv=0' The patch has now been corrected to deal with this case. A incremental patch is attached to this message. Regards Henrik keep-alive.patch _ MSN Hotmail, o maior webmail do Brasil. http://www.hotmail.com
RE: [squid-users] Impossible keep-alive header
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 give some details on when you see this problem, and if you are using any parent proxies or not. Regards Henrik
RE: [squid-users] Impossible keep-alive header
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 19:38:38| ctx: enter level 0: 'http://applications.atpco.net/extranet/coresystems/pdf/fm_rules_n3_b.pdf' 2004/01/23 19:38:38| httpProcessReplyHeader: Impossible keep-alive header from 'http://applications.atpco.net/extranet/coresystems/pdf/fm_rules_n3_b.pdf' and I used one patch that you sent (keep-alive.patch ) and the warning decreased from 1 warning per 10 seconds to 1 warning per 4 or 5 hours (acceptble). Today I have compiled squid-2.5.STABLE4-20040123.tar.bz2 to know if the problem was solved but the cache.log file starts to increase those warnings. My topology: I have two proxies that work together on the same LAN as MASTER/BACKUP SERVERs using HeartBeat. For users we have just one Proxy but if something happens to him, the another one will promptly assume all traffic. As we have an average of 4500 users, I force Proxy 1 to use Proxy 2 as a parent proxy so Proxy 2 can full its cache. When I start doing this configuration I had a problem that a solved using this line at my squid.conf icp_query_timeout 2000 I dont know if this is the best configuration to do this kind of topology but is working and any comments suggestions are welcome!! Let me know if you need more details or configs. I use slackware 9.1 with kernel 2.4.24 two PROLIANT ML350 servers with 2 G of RAM and 30 G of cache. Many thanks in advance and congratulations for your great job, Leon. _ MSN Hotmail, o maior webmail do Brasil. http://www.hotmail.com
RE: [squid-users] Impossible keep-alive header
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 the cache.log file: 2004/01/19 10:58:34| ctx: enter level 0: 'http://wisapidata.weatherbug.com/WxAlertIsapi/WxAlertIsapi.cgi?GetAlert30Magic=1ZipCode=27519StationID=RALGHUnits=0RegNum=27560925Version=5.02t=1074526042lv=0' 2004/01/19 10:58:34| httpProcessReplyHeader: Impossible keep-alive header from 'http://wisapidata.weatherbug.com/WxAlertIsapi/WxAlertIsapi.cgi?GetAlert30Magic=1ZipCode=27519StationID=RALGHUnits=0RegNum=27560925Version=5.02t=1074526042lv=0' 2004/01/19 10:58:34| ctx: exit level 0 The corresponding access.log entry says: 10.23.11.86 - - [19/Jan/2004:10:59:34 -0500] GET http://wisapidata.weatherbug.com/WxAlertIsapi/WxAlertIsapi.cgi?GetAlert30Magic=1ZipCode=27519StationID=RALGHUnits=0RegNum=28333984Version=3.0t=1074525302lv=0 HTTP/1.0 200 236 TCP_MISS:DEFAULT_PARENT Mike Mitchell SAS Institute Inc. [EMAIL PROTECTED] (919) 531-6793 -Original Message- From: Henrik Nordstrom [mailto:[EMAIL PROTECTED] Sent: 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 headers are impossible was a little too broad, sometimes triggering on fully valid HTTP/1.0 replies. The patch has been corrected, and attached to this message you can find the incremental patch if you are using the snapshot release or otherwise can't easily get/apply the updated patch. Regards Henrik
RE: [squid-users] Impossible keep-alive header
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 the cache.log file: 2004/01/19 10:58:34| httpProcessReplyHeader: Impossible keep-alive header from 'http://wisapidata.weatherbug.com/WxAlertIsapi/WxAlertIsapi.cgi?GetAlert30Magic=1ZipCode=27519StationID=RALGHUnits=0RegNum=27560925Version=5.02t=1074526042lv=0' Problem confirmed. Patch pending. Regards Henrik
RE: [squid-users] Impossible keep-alive header
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 the cache.log file:
2004/01/19 10:58:34| httpProcessReplyHeader: Impossible keep-alive header from
'http://wisapidata.weatherbug.com/WxAlertIsapi/WxAlertIsapi.cgi?GetAlert30Magic=1ZipCode=27519StationID=RALGHUnits=0RegNum=27560925Version=5.02t=1074526042lv=0'
The patch has now been corrected to deal with this case. A incremental
patch is attached to this message.
Regards
Henrik
Index: src/HttpMsg.c
===
RCS file: /server/cvs-server/squid/squid/src/HttpMsg.c,v
retrieving revision 1.10
retrieving revision 1.10.2.1
diff -u -r1.10 -r1.10.2.1
--- src/HttpMsg.c 12 Jan 2001 00:37:14 - 1.10
+++ src/HttpMsg.c 19 Jan 2004 17:34:36 - 1.10.2.1
@@ -91,6 +91,7 @@
int
httpMsgIsPersistent(http_version_t http_ver, const HttpHeader * hdr)
{
+#if WHEN_SQUID_IS_NOT_HTTP1_1
if ((http_ver.major = 1) (http_ver.minor = 1)) {
/*
* for modern versions of HTTP: persistent unless there is
@@ -98,6 +99,9 @@
*/
return !httpHeaderHasConnDir(hdr, close);
} else {
+#else
+{
+#endif
/*
* Persistent connections in Netscape 3.x are allegedly broken,
* return false if it is a browser connection. If there is a
RE: [squid-users] Impossible keep-alive header
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 ? Yes. All patches on the published patches page is automatically incorporated in the daily snapshots. Both represent different views of the Squid CVS source tree. Regards Henrik
Re: [squid-users] Impossible keep-alive header
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| 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: Impossible keep-alive header from 'http://www.squid-cache.org/Versions/v2/2.5/bugs/' This is on a Red Hat v9 system, running Squid 2.5S4 and all patches applied. I think that these many entries in cache.log are the result of applying the recent squid-2.5.STABLE4-http_workarounds.patch patch. Anyone else seeing this behavior? Thanks. Sent using Mulberry 3.01a
Re: [squid-users] Impossible keep-alive header
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: Impossible keep-alive header from 'http://www.squid-cache.org/Versions/v2/2.5/bugs/' Do you have a parent proxy? If you do, what kind of proxy? Regards Henrik
Re: [squid-users] Impossible keep-alive header
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 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| 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: Impossible keep-alive header from 'http://www.squid-cache.org/Versions/v2/2.5/bugs/' This is on a Red Hat v9 system, running Squid 2.5S4 and all patches applied. I think that these many entries in cache.log are the result of applying the recent squid-2.5.STABLE4-http_workarounds.patch patch. Anyone else seeing this behavior? Thanks. Sent using Mulberry 3.01a
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 headers are impossible was a
little too broad, sometimes triggering on fully valid HTTP/1.0 replies.
The patch has been corrected, and attached to this message you can find
the incremental patch if you are using the snapshot release or otherwise
can't easily get/apply the updated patch.
Regards
Henrik
Index: src/http.c
===
RCS file: /server/cvs-server/squid/squid/src/http.c,v
retrieving revision 1.384.2.10
diff -u -p -r1.384.2.10 http.c
--- src/http.c 12 Jan 2004 10:51:59 - 1.384.2.10
+++ src/http.c 14 Jan 2004 18:34:53 -
@@ -476,7 +476,7 @@ httpProcessReplyHeader(HttpStateData * h
if (reply-keep_alive) {
if (httpState-peer)
httpState-peer-stats.n_keepalives_recv++;
- if (reply-content_length == -1) {
+ if (httpReplyBodySize(httpState-request-method, reply) == -1) {
debug(11, 1) (httpProcessReplyHeader: Impossible keep-alive header from
'%s'\n, storeUrl(entry));
httpState-flags.keepalive_broken = 1;
}
Index: src/structs.h
===
RCS file: /server/cvs-server/squid/squid/src/structs.h,v
retrieving revision 1.408.2.19
diff -u -p -r1.408.2.19 structs.h
--- src/structs.h 12 Jan 2004 10:51:59 - 1.408.2.19
+++ src/structs.h 14 Jan 2004 18:34:53 -
@@ -964,11 +964,11 @@ struct _HttpReply {
};
struct _http_state_flags {
-unsigned int keepalive_broken:1;
-unsigned int abuse_detected:1;
unsigned int proxying:1;
unsigned int keepalive:1;
unsigned int only_if_cached:1;
+unsigned int keepalive_broken:1;
+unsigned int abuse_detected:1;
};
struct _HttpStateData {
