RE: [squid-users] Can't controle adaptation_access properly in ICAP.

Could anyone ask something please?

I have a bit information for this case.
When I configure only one ACL at the adaptation_access, it worked fine.
As bellow, Squid's icap client didn't activate for only eicar ACL and
another ACL was activated.

# This is OK.
adaptation_access svcBlocker deny eicar
#adaptation_access svcBlocker deny trend --->commented

I think that this problem emerges, when two more adaptation_access is used
for a service_set.

Best Regards,
Seiji Kobayashi

-----Original Message-----
From: S.KOBAYASHI [mailto:kobayashi_at_e-trees.jp]
Sent: Tuesday, August 12, 2008 5:21 PM
To: squid-users_at_squid-cache.org
Subject: [squid-users] Can't controle adaptation_access properly in ICAP.

Dear developer,

I'm using the squid-3.HEAD-20080811, and trying to activate 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.

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 a lack of software, or my
configuration is something wrong?

Best Regards,
Seiji Kobayashi
Received on Thu Aug 14 2008 - 00:19:04 MDT