ERR_CLIENT_ABORT bug.

Hi, i'm using either squid 1.0.18 or 1.1beta8 , my "access.log" is full
of ERR_CLIENT_ABORT ... so i decided to clean it and to test it ...

I started squid 1.0.18 or 1.1beta8 and opened a netscape 3.0 and i just typed
the URL "http://www.nlanr.net/Squid/" , i waited for the page to download
and didn't interrupt it , the page looked good and i looked into
the access.log i saw some ERR_CLIENT_ABORT and in "store.log" i saw that
, because of that error , most of my GETs was released (not stored in the
cache)...

I decided to grab more URLs and i found that i got more & more
ERR_CLIENT_ABORT but
only on some http servers, i tried to raise the log level (ALL,9) but i
didn't find
where (in which function) the ERR_CLIENT_ABORT was set...

My guess is that some replys from http servers make squid set ERR_CLIENT_ABORT
without any good reason... because when i made the test again it happend on
the
same URL (same gifs, or same jpegs) ...

I tried to change some options in my squid.conf (quick_abort , timeouts
...) but
i still had the same problem...

This bug has something weird:

When you get a real ERR_CLIENT_ABORT it's written in "cache.log" &
"access.log"
but when you get a bogus ERR_CLIENT_ABORT it's only written in "access.log"
...

There is also a difference between what is written during a real & bogus
ERR_CLIENT ABORT,
here is an example:

REAL ERR_CLIENT_ABORT: (i hit stop during the download)
        access.log:
                194.250.215.11 - - [21/Oct/1996:01:58:26 +0100] "GET
http://www.ececs.uc.edu/~bbirtle/previews/and_prev.gif" ERR_CLIENT_ABORT 0
        cache.log:
                96/10/21 01:58:31| ERR_CLIENT_ABORT:
http://www.ececs.uc.edu/~bbirtle/previews/and_prev.gif
        store.log:
                845859511.386 RELEASE 400 300 [ 5m] 0/1368
67/GET/http://www.ececs.uc.edu/~bbirtle/previews/and_prev.gif

BOGUS ERR_CLIENT_ABORT: (i didn't interrupt it !)
        access.log:
                194.250.215.11 - - [21/Oct/1996:01:59:39 +0100] "GET
http://www.ececs.uc.edu/~bbirtle/gui/bg2.gif" ERR_CLIENT_ABORT 88
        cache.log:
                nothing
        store.log:
                845859579.781 RELEASE 304 0 [ 0s] 0/0
81/GET/http://www.ececs.uc.edu/~bbirtle/gui/bg2.gif

This bug doesn't make squid crash, it doesn't corrupt anything, you can't
see it if
you don't look into the logs, but the bad thing is that many cachable URLs
are never
cached... because when the bug happens on an URL this URL is always
released...

Did anyone already see that bug ?

Thanks for any help/reply :)
Received on Sun Oct 20 1996 - 17:24:41 MDT