Re: [squid-users] is squid 3.1.x is multiple chained ICAP server compliance ?

David Touzeau wrote:
> dear
>
> i have 3 ICAP services
>
> first Kaspersky, second C-ICAP+clamav and third C-ICAP+SquidGuard.
>
> It seems that Squid only use the first one has Kaspersky First for the
> respmod
>
> Url are correctly checked because it use only the reqmod but it seems
> that the 2 respmod AV services are not chained.
>
> Is squid 3.1 is multiple ICAP respmod compliance or is it only a
> failover feature.
>

I believe its full compliance. Have not read the RFCs in detail though.

You seem to have a mix-up between the types though.

SET is a collection of redundant services, first-connected-wins.

CHAIN is a sequential order of services to be applied one after another.

What you want is something simple like this:

# --------- ICAP AV Scanners

icap_service kav_resp respmod_precache routing=on bypass=on
icap://127.0.0.1:1344/av/respmod

icap_service clamav_resp respmod_precache routing=on bypass=on
icap://127.0.0.1:1345/srv_clamav

# --------- adaptation

adaptation_service_chain AV_scan kav_resp clamav_resp

adaptation_access AV_scan deny MULTIMEDIA
adaptation_access AV_scan allow all

I'm not sure how the squidguard service will plug in.

Amos

-- 
Please be using
   Current Stable Squid 2.7.STABLE9 or 3.1.7
   Beta testers wanted for 3.2.0.1