Re: icpDetectClientClose: FD 16, 256 unexpected bytes

From: Joe Ramey <>
Date: Wed, 30 Oct 1996 11:37:00 -0600

   Date: Tue, 29 Oct 1996 17:01:22 +0100 (MET)
   From: Thorvaldur Arnarson <>
   X-Sender: valdi@oden
   Mime-Version: 1.0
   Content-Type: TEXT/PLAIN; charset=ISO-8859-1
   Content-Transfer-Encoding: QUOTED-PRINTABLE
   X-Mailing-List: <> archive/latest/527
   Precedence: list


   I have been running squid for some time now, but recently I've
   received these error messages in my syslog:

   Oct 29 10:04:02 wwwproxy squid[464]: [29/Oct/1996:10:04:01 +0100]
   icp.c:198= 2:^I icpDetectClientClose: FD 17, 256 unexpected bytes

   These messages usually come in short storms, e.g. 20 messages over
   2 minute= s interval. This can result in that the proxy hangs, and
   the only thing to do=
   to restart the cache. Unfortunately this happens quite often, 3-4
   times a w= eek. I were running squid 1.0.8 and because of this
   problem upgraded to 1.0.18 b= ut without any success.

   Is this a configuration problem or a bug?

   /Thorvaldur =D6rn Arnarson=20

I've done a little debugging of this and think that it's caused by
clients trying to use persistent connections. I added code to squid
to print out the `unexpected bytes' that it received and they
typically look something like this:

Proxy-Connection: Keep-Alive
User-Agent: Mozilla/2.02 (Win95; I)
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg

I don't know enough about the Netscape client to know why it does this
sometimes and apparently not at other times, or if there's anything
squid can do about it.
Received on Wed Oct 30 1996 - 09:38:32 MST

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:33:24 MST