Unable to configure ICAP

[Lorenzo Milesi]

Hi.

I've successfully set up Squid with Kerberos and NTLM auth, and apparently works well. I was trying to pass the authenticated user info to E2 inn order to create a block group but so far I haven't managed to get it working. When I enable it on the browser I get an icap communication error page, with just [No Error] as a message.

I also tried this thread but cache_peer doesn't send the credentials to Squid, or at least I wasn't getting them in access.log.

Thanks

In e2guardian.conf I have:

icapport = 1344

In squid.conf I have:

icap_enable on
icap_service service_req reqmod_precache bypass=0 icap://127.0.0.1:1344/request
icap_service service_resp respmod_precache bypass=0 icap://127.0.0.1:1344/response
adaptation_access service_req allow all
adaptation_access service_resp allow all
icap_send_client_ip on
icap_send_client_username on
adaptation_masterx_shared_names X-ICAP-E2G
icap_log /var/log/squid/icap2.log

[John Richards]

Hi Lorenzo,

Squid will notice if the ICAP server isn't there and remembers that for some time and doesn't retry to connect for minutes.

I've hit a similar problem when e2guardian was down, squid notices and I would get that ICAP error in the browser for quite some time even though e2guardian was running and listening on port 1344.

Make sure e2guardian is running and restart squid.

Worth a try.