On 2024-01-10 16:48, Dave Dykstra wrote:
https://github.com/squid-cache/squid/security/advisories/GHSA-rj5h-46j6-q2g5.
... is another workaround to disable TRACE requests ...?
AFAICT, denying TRACE requests will not allow TRACE transactions to
reach the problematic code related to that Ad
We currently are unable to upgrade to squid6 due to a serious problem we found
with collapsed_forwarding (https://bugs.squid-cache.org/show_bug.cgi?id=5332),
and our applications need collapsed_forwarding for reasonable performance.
So we want to build a version of squid5 with as many vulnerabil
On 2024-01-10 09:21, Arun Kumar wrote:
i) Retry seems to fetch one chunk of the response and not the complete.
ii) Enabling sslbump and turning ICAP off, not helping.
iii) gcc version is 7.3.1 (Red Hat 7.3.1-17)
GCC v7 has insufficient C++17 support. I recommend installing GCC v9 or
better an
On 2024-01-09 19:32, John Zhu wrote:
We have the same “suspension” issue when “too many failure”.
To clarify, you have a "failure" issue. Suspension after
icap_service_failure_limit is normal/expected.
https://www.mail-archive.com/squid-users@lists.squid-cache.org/msg22187.html
FWIW, AF
i) Retry seems to fetch one chunk of the response and not the complete.ii)
Enabling sslbump and turning ICAP off, not helping. iii) gcc version is 7.3.1
(Red Hat 7.3.1-17)
Also want to point out that, squid connects to another non-squid proxy to reach
internet.cache_peer parent 0 no-query de
On 09/01/2024 15:42, Alex Rousskov wrote:
On 2024-01-09 05:56, Stephen Borrill wrote:
On 09/01/2024 09:51, Stephen Borrill wrote:
On 09/01/2024 03:41, Alex Rousskov wrote:
On 2024-01-08 08:31, Stephen Borrill wrote:
I'm trying to determine why squid 6.x (seen with 6.5) connected via
IPv4-only
