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?GetAlert30&Magic=1&ZipCode=27519&StationID=RALGH&Units=0&RegNum=27560925&Version=5.02&t=1074526042&lv=0' 2004/01/19 10:58:34| httpProcessReplyHeader: Impossible keep-alive header from 'http://wisapidata.weatherbug.com/WxAlertIsapi/WxAlertIsapi.cgi?GetAlert30&Magic=1&ZipCode=27519&StationID=RALGH&Units=0&RegNum=27560925&Version=5.02&t=1074526042&lv=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?GetAlert30&Magic=1&ZipCode=27519&StationID=RALGH&Units=0&RegNum=28333984&Version=3.0&t=1074525302&lv=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
