On 01/27/2018 10:47 AM, Yuri wrote: > He's just disabled icap-based service without disabling icap itself. So > - yes - this is as expected. The above logic is flawed: Vieri told Squid to bypass (bypassable) ICAP errors, but Squid did not bypass an ICAP error. Whether that outcome is expected depends on whether that specific ICAP error was bypassable. Yes, I understand that c-icap did not successfully process the message after clamd went down, but that fact is not important here. What is important here is how c-icap relayed that problem to Squid. That part I do not know, so I cannot say whether Squid just could not bypass this particular ICAP problem (i.e., Squid behavior is expected) or there is a bug in Squid's bypass code. > bupass=1 permit squid to bypass > adaptation in case of overloading icap service. Yes, but service overload is _not_ the only problem that bypass=1 can bypass. The documentation for that option describes the option scope: > If set to 'on' or '1', the ICAP service is treated as > optional. If the service cannot be reached or malfunctions, > Squid will try to ignore any errors and process the message as > if the service was not enabled. No all ICAP errors can be > bypassed. If set to 0, the ICAP service is treated as > essential and all ICAP errors will result in an error page > returned to the HTTP client. > > Bypass is off by default: services are treated as essential. Alex. _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
