[squid-users] After upgrade from squid6.6 to 6.8 we have a lot of ICAP_ERR_OTHER and ICAP_ERR_GONE messages in icap logfiles

[Amos Jeffries]

On 12/03/24 04:31, Dieter Bloms wrote:
> Hello,
> 
> after an upgrade from squid6.6 to squid6.8 on a debian bookworm we have a lot
> of messages from type:
> 
> ICAP_ERR_GONE/000
> ICAP_ERR_OTHER/200
> ICAP_ERR_OTHER/408
> ICAP_ERR_OTHER/204
> 
> and some of our users claim about bad performance and some get "empty
> pages".
> Unfortunately it is not deterministic, the page will appear the next
> time it is called up. I can't see anything conspicuous in the cache.log.
> 

Hmm, there was 
<https://github.com/squid-cache/squid/commit/4658d0fc049738c2e6cd25fc0af10e820cf4c11a> 
changing message I/O in particular. The behavioural changes from that 
might have impacted ICAP in some unexpected way.

Also, if you are using SSL-Bump to enable virus scanning then 
<https://github.com/squid-cache/squid/commit/debf3f17be7761ea4992864a828f42ee773dfbaf> 
might also be having effects.

HTH
Amos