[squid-users] ICAP 500 is not bypassed

[Alex Rousskov]

On 01/29/2018 01:01 AM, Vieri wrote:

> I reproduced the problem, and saw that the c-icap server (or its
> squidclamav module) reports a 500 internal server error when clamd is
> down. I guess that's not bypassable?

The ICAP 500 status code does not preclude bypass. In fact, your Squid
attempts to bypass this ICAP server error:


> 2018/01/29 08:30:01.479 ... bypassing ... exception: Unsupported ICAP status code


Unfortunately, Squid bypass code then triggers an internal exception
which kills the bypass attempt and ends the HTTP transaction with
ICAP_ERR_OTHER:

> 2018/01/29 08:30:01.480 ... Throw: ModXact.cc:1848: exception: !disabled()
> 2018/01/29 08:30:01.480 ... Warning: reseting outcome: from ICAP_ECHO to ICAP_ERR_OTHER

That second exception looks like a Squid bug to me, but I have not
investigated it enough to be sure about that designation (not to mention
propose a fix). Your next steps revolve around these standard options:

https://wiki.squid-cache.org/SquidFaq/AboutSquid#How_to_add_a_new_Squid_feature.2C_enhance.2C_of_fix_something.3F


HTH,

Alex.