Ah, I had presumes that squid would just retry on the next request. You dont use bypass for either reqmod_precache or respmod_precache? Sean On 4 December 2012 16:08, Eliezer Croitoru <eliezer@xxxxxxxxxxxx> wrote: > Unless you have problems such as the bug mentioned or any other reason dont > use the bypass. > > Be ware that bypass leave you with with no knowledge about existing problem. > You can have ICAP service almost "OFF" for weeks and you will not know about > it. > > Regards, > Eliezer > > > On 12/4/2012 4:55 PM, Sean Boran wrote: >> >> HI, >> >> I'm now running HEAD (for latest SSL bump fixes) on revision 8886 on a >> new box pulled last Friday, so may it has those fixed. The above bug >> was from HEAD from early august. >> >> If that does not help, I'll try "icap_persistent_connections off". >> >> I also found ready that one should have "bypass=1" to ensure squid >> continue if it cannot talk to icap? >> >> icap_service service_req reqmod_precache bypass=1 >> icap://127.0.0.1:1344/squidclamav >> icap_service service_resp respmod_precache bypass=1 >> icap://127.0.0.1:1344/squidclamav >> >> Thanks, >> >> Sean > > > -- > Eliezer Croitoru > https://www1.ngtech.co.il > sip:ngtech@xxxxxxxxxxxx > IT consulting for Nonprofit organizations > eliezer <at> ngtech.co.il
