Rui, Thanks for the input again !!!!
I was using icap://<savse_server>:1344/respmod, instead of avscan .... I changed it, and it worked, for a while .... I was using the icap_streaming patch, and it worked for a while, then it complained about something like a 0 byte response from the icap server .... I tried again, rebuilding squid from scratch with the icap-2.5 patch, done the icap configuration that you suggested, but, when I tried to read my first web page, squid just died with a laconic "Aborted" message .... What version of squid are you running with icap and SavSe? Are you from Brazil ... Your name suggests it .... Thanks in Advance, Carlos Zottmann. ----------------------------------------------- Hi Carlos, I've been using the following configuration with success with all squid icap versions: #################startconfiguration########################### icap_enable on icap_service avscan respmod_precache 0 icap://<savse_server>:1344/avscan icap_class avclass avscan # Don't scan traffic to the SAVSE server, there's a bug that won't allow you # to access teh admin interface of SAVSE through the Squid proxy acl savse_server dst <savse_server_ip>/255.255.255.255 icap_access avclass deny savse_server # Send all other traffic to SAVSE and let SAVSE decide what to scan icap_access avclass allow all #################end configuration########################### Currently Symantec Scan Engine hasn't been tested in REQMOD with Squid, Squid ICAP doesn't currently support scan of POST requests in REQMOD, although from version 4.3 REQMOD AV scanning is supported in Symantec Scan Engine, The correct syntax should be icap_service avscan reqmod_precache 0 icap://<savse_server>:1344/avscanreq Regards, Rui _________________________________________________________ Voce quer um iGMail protegido contra vírus e spams? Clique aqui: http://www.igmailseguro.ig.com.br Ofertas imperdíveis! Link: http://www.americanas.com.br/ig/
