If you experience Squid "ICAP protocol error" (with bypass enabled) please consider increasing the c-icap following parameters: StartServers, MaxServers, MinSpareThreads, MaxSpareThreads, ThreadsPerChild. Are these settings outdated? I also see recomendations from ClamAV: In fact, I can't find them in any squid configuration file. Icap_service service_resp respmod_precache bypass=1 icap://127.0.0.1:1344/squidclamavīut I don't see those lines in squid.inc. Icap_service service_req reqmod_precache bypass=1 icap://127.0.0.1:1344/squidclamav Icap_service service_resp respmod_precache bypass=0 icap://127.0.0.1:1344/squidclamav Icap_service service_req reqmod_precache bypass=0 icap://127.0.0.1:1344/squidclamav I have read many posts about the first line of defense is to put Squid in bypass mode by making the following modifications to squid.inc: I hit the site at work and it loads fine, no warnings about the site being untoward in any way. ![]() I turn off ClamAV and it loads fine (no surprise). So far, it only happens on this site, but it happens consistently on this site. Every time I try to hit, I get an ICAP error. ![]() ![]() It's all running great with one possible exception. I recently implemented an SG-3100 and have added Squid (with ClamAV), SquidGuard and Suricata.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |