Hi,
S.KOBAYASHI wrote:
Dear developer,
I'm using the squid-3.HEAD-20080811, and trying to deliver icap connections
properly as I expected.
It means to activate icap or not by using adaptation_access with ACL.
However, adaptation_access didn't seem worked properly.
Yes this is a squid3-HEAD bug. This bug does not exists in squid-3.0.
Can you fill a bug report? Squid bugzilla is at:
http://bugs.squid-cache.org/
Regards,
Christos
I configured ICAP settings as below.
acl eicar url_regex http://www.eicar.org/
acl trend url_regex http://www.trendmicro.co.jp/
icap_service service_1 respmod_precache 0
icap://192.168.10.231:1344/interscan
icap_service service_2 respmod_precache 0
icap://192.168.10.232:1344/interscan
adaptation_service_set svcBlocker service_1 service_2
adaptation_access svcBlocker deny eicar
adaptation_access svcBlocker deny trend
#adaptation_access svcBlocker allow all --> commented
In this case, squid did activate both eicar and trend, and then connected to
the ICAP server.
I'm wondering, if adaptation_access has lack of software, or my
configuration is something wrong?
Best Regards,
Seiji Kobayashi
