It's been 5 years since this was originally posted, but I am currently
in the process of upgrading from Squid 4.13 to 5.8, and have
encountered the same scenario when running our integration tests to
validate the existing behavior. To summarize, given the exact same
configuration in both versions,
On 8/9/23 08:14, Tommy Brunn wrote:
It's been 5 years since this was originally posted, but I am currently
in the process of upgrading from Squid 4.13 to 5.8,
FWIW, you should be upgrading to v6 instead. Squid v5 maintainer does
not expect making regular bug-fixing v5 releases:
https://githu
Thank you for the quick response and confirmation that this is indeed
a bug. I have since confirmed that the same bug is present also in
6.1.
On Wed, Aug 9, 2023 at 3:38 PM Alex Rousskov wrote:
> Thank you for sharing those details. When developers start working on a
> fix, they may find them ver
Hi,
we have been having some issues lately with our Squid proxies on version 6.1.
We also have the patch for the REQMOD satisfaction regression installed:
https://github.com/squid-cache/squid/pull/1400
The issue:
When there is a request sent to the ICAP server and the ICAP server is replying
On 8/9/23 14:33, mail...@fuchus.de wrote:
Do you have any remarks on the change? Maybe you have some more
insight on the interplay of the code or what seems to be causing the
issue in detail.
Hi Leonardo,
I do, but this mailing list is not the best place to discuss Squid
code. If you w
