Mitko Stoyanov wrote:
Good day, I have the following ICAP setup as below, and the traffic which is not supposed to be sent to the ICAP server (filter_video) somehow still makes it there..A quick Google scan shows that there are some bugs submitted in this area, but is not clear whether the ACL issues are now fixed.
If the bugs you have found contin a comment like "Applied to Squid 3.0" they are fixed in 3.0 from that date, otherwise only in 3.1 or not yet.
My Squid version is 3.0STABLE11-20090112. acl filter_video dstdomain .xxx.xxx.au ........... #Kaspersky kav4proxy icap settings icap_enable on icap_send_client_ip on icap_service is_kav_resp respmod_precache 1 icap://xxx.xxx.xxx.xxx:1344/av/respmod icap_service is_kav_req reqmod_precache 1 icap://xxx.xxx.xxx.xxx:1344/av/reqmod icap_class ic_kav_req is_kav_req icap_class ic_kav_resp is_kav_resp icap_access ic_kav_resp deny filter_video icap_access ic_kav_req deny filter_video icap_access ic_kav_resp allow all icap_access ic_kav_req allow all
Amos -- Please be using Current Stable Squid 2.7.STABLE6 or 3.0.STABLE13 Current Beta Squid 3.1.0.6
