> Would it be better to postpone the re-enabling / to a later stage
> stopReceiving()?
>
>
That was meant to be:
"Would it be better to postpone the re-enabling / stopReceiving() to a
later stage?"
Sorry for the typo.
___
squid-dev mailing list
>> Could you please give me some advice on a better/proper fix, if close()
>> at "abandoning" time is wrong?
>
> Unfortunately, I cannot.
In fact, your message was very helpful! Thank you.
> In general, responding with a 403 does not invalidate the client
> connection, so it does not have to be
: [squid-dev] File descriptor leak at ICAP reqmod rewrites of
CONNECT requests
On 12/10/20 3:33 PM, Alexey Sergin wrote:
> - Squid writes to cache.log a message like "kick abandoning <>";
These messages indicate a Squid bug, most likely in REQMOD request
satisfaction impl
> clients requests will bock less and..
>
> It will probably consume less then the ICAP connections memory leak.
>
>
>
> Waiting,
>
> Eliezer
>
>
>
>
>
> Eliezer Croitoru
>
> Tech Support
>
> Mobile: +972-5-28704261
>
> Email: ngtech1...@gmail.com
On 12/10/20 3:33 PM, Alexey Sergin wrote:
> - Squid writes to cache.log a message like "kick abandoning <>";
These messages indicate a Squid bug, most likely in REQMOD request
satisfaction implementation specific to CONNECT use cases. The messages
are not prefixed with a "BUG" label, but
aiting,
Eliezer
Eliezer Croitoru
Tech Support
Mobile: +972-5-28704261
Email: ngtech1...@gmail.com <mailto:ngtech1...@gmail.com>
From: squid-dev On Behalf Of Alexey
Sergin
Sent: Thursday, December 10, 2020 10:33 PM
To: squid-dev@lists.squid-cache.org
Subject: [squid-dev] File des
Hello Squid Developers.
I'm a software engineer.
My team uses Squid with an ICAP server. We have noticed that Squid leaks
file descriptor and memory when (reqmod) ICAP server replies with http "403
Forbidden" on http CONNECT request.
Here is a step-by-step description of the problematic
