Hi, I reproduced the problem, and saw that the c-icap server (or its squidclamav module) reports a 500 internal server error when clamd is down. I guess that's not bypassable? The c-icap server log reports: Mon Jan 29 08:30:35 2018, 5134/1290311424, squidclamav.c(1934) dconnect: Mon Jan 29 08:30:35 2018, 5134/1290311424, entering. Mon Jan 29 08:30:35 2018, 5134/1290311424, squidclamav.c(2015) connectINET: Mon Jan 29 08:30:35 2018, 5134/1290311424, ERROR Can't connect on 127.0.0.1:3310. Mon Jan 29 08:30:35 2018, 5134/1290311424, squidclamav.c(2015) connectINET: Mon Jan 29 08:30:35 2018, 5134/1290311424, ERROR Can't connect on 127.0.0.1:3310. Mon Jan 29 08:30:35 2018, 5134/1290311424, squidclamav.c(744) squidclamav_end_of_data_handler: Mon Jan 29 08:30:35 2018, 5134/1290311424, ERROR Can't connect to Clamd daemon. Mon Jan 29 08:30:35 2018, 5134/1290311424, An error occured in end-of-data handler !return code : -1, req->allow204=1, req->allow206=0 Here's Squid's log: https://drive.google.com/file/d/18HmM8pOuDQmE4W_vwmSncXEeJSvgDjDo/view?usp=sharing I was hoping I could relate this to the original topic, but I'm afraid they are two different issues. Thanks, Vieri _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
