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

On 28/08/2010 05:34, Amos Jeffries wrote:
> adaptation_access AV_scan deny MULTIMEDIA
> adaptation_access AV_scan allow all

Amos, your are the king of squid specialists !!!
It's working like a charm !

SquidGard is supported by C-ICAP so you can provide URL filtering using
ICAP protocol that provides better performances.

Here it is my final configuration for others guys that requesting using
multiple ICAP servers in chain mode :
Amos, if you found some tips to tweaks this config, let me know...

acl MULTIMEDIA rep_mime_type -i
^(audio\/x-mpegurl|audio\/mpeg|video\/flv|video\/x-flv|application\/x-shockwave-flash|audio\/ogg|video\/ogg|application\/ogg)$

# --------- ICAP Services.(2 service(s))
# --------- icap_service C-ICAP mode 3.1.x
# --------- icap_service C-ICAP + SquidGuard
icap_service service_url_check reqmod_precache routing=on bypass=on
icap://127.0.0.1:1345/url_check
icap_service service_antivir respmod_precache routing=on bypass=on
icap://127.0.0.1:1345/srv_clamav

# --------- icap_service KASPERSKY mode 3.1.1

icap_service is_kav_resp respmod_precache routing=on bypass=on
icap://127.0.0.1:1344/av/respmod
icap_service is_kav_req reqmod_precache routing=on bypass=on
icap://127.0.0.1:1344/av/reqmod

# --------- adaptation chain services.
adaptation_service_chain ANTIVIRUS_CHAINS service_antivir is_kav_resp
adaptation_access ANTIVIRUS_CHAINS deny MULTIMEDIA
adaptation_access ANTIVIRUS_CHAINS allow all

adaptation_service_chain REQ_CHAINS service_url_check is_kav_req
adaptation_access REQ_CHAINS allow all

icap_enable on
icap_preview_size 128
icap_service_failure_limit -1
icap_preview_enable on
icap_send_client_ip on
icap_send_client_username on
icap_client_username_header X-Authenticated-User
icap_client_username_encode on
Received on Sat Aug 28 2010 - 12:33:47 MDT