Hi Amos I can actually see this abandoning-messages just for CONNECT-Requests (and as much as I have investigated -> only for these). Sometimes, there is a 407 before, and sometimes there is just a CONNECT-Request (probably the browser send the authentication-challenge properly within the request). In my case, it looks like this: CACHE.LOG ========= 2013/06/20 12:02:34 kid4| abandoning local=172.xx.xx.xx:3128 remote=10.xx.xx.xx:57286 FD 23926 flags=1 ACCESS.LOG ========== [Thu Jun 20 12:02:34 2013].773 0 10.xx.xx.xx TCP_DENIED/407 3768 CONNECT geo.gateway.messenger.live.com:443 - HIER_NONE/- text/html [Thu Jun 20 12:02:34 2013].785 7 10.xx.xx.xx NONE/200 5543 CONNECT geo.gateway.messenger.live.com:443 USER HIER_NONE/- text/html The message appears not only for a certain URL. The message appears generally for some (not all) CONNECT-Requests (URL independent). Kind regards, Tom On Thu, Jun 20, 2013 at 10:53 AM, Amos Jeffries <squid3@xxxxxxxxxxxxx> wrote: > On 20/06/2013 5:26 p.m., Tom Tom wrote: >> >> Hi >> >> In the cache.log (squid 3.3.4), I sometimes get some "abandoning"-messages >> like: >> abandoning local=172.xx.xx.xx:3128 remote=10.xx.xx.xx:52548 FD 35 flags=1 >> >> It seems, that this message only appers with https resp. CONNECT-Requests. >> >> What could be a reason for this "abandoning"-message? How can I prevent >> them? > > > We are still trying to figure out the exact causes of these. They can occur > from a few potential reasons. Something strange has gone on while parsing a > request. My own suspicion is that they are the result of CONNECT request > being parsed, processed and responded to (DENIED or an auth challenge are > usually the last thing seen on these connections) within a single call to > the parser. > > These do not appear to be worth worrying much over but if you are interested > in contributing to a smoother running Squid some assistance figuring out how > your partiular ones are occuring is welcome. > > Amos
