[squid-users] Squid and c-icap's srv_url_check module

[Amiq Nahas]

On Fri, Jun 19, 2020 at 4:20 PM Amos Jeffries <squid3 at treenet.co.nz> wrote:
>
> On 19/06/20 10:07 pm, Amiq Nahas wrote:
> >> Looks like traffic is fine and Squid operational, but no sign of any
> >> ICAP activity. I think try adding this to your config:
> >>
> >>   adaptation_access svcBlocker allow all
> >>
> >> Its supposed to be the default action, but just to be sure add it
> >> explicitly.
> >
> > I added the above line and browser could not open any page, this was
> > the notice shown: https://ibb.co/HVQYD2c
> > cache.log: https://justpaste.it/38eyl
> > access.log: https://paste.debian.net/1152817/
> >
>
> The problem is this:
>
> "
> 2020/06/19 15:11:09.998 kid1| 93,2| Xaction.cc(272)
> dieOnConnectionFailure: Adaptation::Icap::OptXact failed to connect to
> icap://127.0.0.1:1344/srv_url_check
>
> 2020/06/19 15:11:09.998 kid1| essential ICAP service is down after an
> options fetch failure: icap://127.0.0.1:1344/srv_url_check [down,!opt]
> "
>
> Next step is to debug why the OPTIONS request to the ICAP service causes
> it to break.

Problem solved. The name of service was wrong.
Service name should be icap://127.0.0.1:1344/url_check instead of
icap://127.0.0.1:1344/srv_url_check.
Thanks for helping in narrowing the problem.