* Niall O'Cuilinn <nocuilinn_at_amdocs.com>:
> I think this is because Squid has received at least one bad response
> from your ICAP server while it was down. As a result it has decided not
> to talk to your ICAP server for a period of time
OK, could be.
> If you want Squid to ignore outages on your ICAP server and always
> attempt a request you can set
>
> icap_service_failure_limit -1
Ah OK, very nice
> Setting this to -1 tells Squid to always connect to ICAP, setting a
> positive number indicates the number of failures allowed before Squid
> stops communicating with Squid. The period of time that Squid stops
> talking to ICAP is controlled by 'icap_service_revival_delay', it is a
> minimum of 30 seconds I think.
Way too long for my purposes.
I tried you suggestion and it works like a charm!
-- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt@charite.de | http://www.charite.deReceived on Tue Apr 13 2010 - 14:48:58 MDT
This archive was generated by hypermail 2.2.0 : Tue Apr 13 2010 - 12:00:04 MDT