[squid-users] bug 4906 issue

[Matus UHLAR - fantomas]

>On 2023-09-26 07:39, Matus UHLAR - fantomas wrote:
>>I have just encountered bug 4906 with squid-4.13 (Debian 11)
>>
>>I could upgrade system fo Debian 12 with squid-5.7 but this issue 
>>doesn't seem to be resolved in it, at least:
>>http://www.squid-cache.org/Versions/v5/changesets/
>>
>>does not mention that.

On 26.09.23 10:09, Alex Rousskov wrote:
>We have not (knowingly) fixed bug 4906 yet. Moreover, there are many 
>other places in Squid code that would result in problems similar to 
>those reported in bug 4906. A comprehensive unofficial fix that 
>addresses the root cause got stuck in my unofficial review queue since 
>December 2019.
[...]
>You can also try a small old unofficial v4.3 workaround patch attached 
>to this email. I do not know whether it will apply to and work with 
>4.13. If you are lucky, this workaround will address the immediate 
>problem in your environment.

Thank you,

the patch itself did not apply cleanly, but only because one difference 
between code.  Modified patch has one line different, and it's not in 
patched code:


-             if (const char *value = (*i)->match(request, al->reply, al)) {
+             if (const char *value = (*i)->match(request, al->reply, NULL)) {


I have compiled the core and seems that the line

acl mon src 10.a.b.c # FGT load balancer check

access_log syslog:local0.info squid !mon

ignores logging requests from 10.a.b.c properly

-- 
Matus UHLAR - fantomas, uhlar at fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety. -- Benjamin Franklin, 1759