Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Due to our user's increasing expertise at downloading virus and the like, we are investigating adding Antivirus to our Squid proxy.

A casual Google reveals several free and one paid:

None of the 'free' ones have reached v1 yet, nor do any inspire huge confidence form their websites (although of course I would rather they spent their time on the app rather than their website!).

Does anybody have experience with any of these (or any other similar apps). If so are they suitable for a production network with 400ish concurrent users, and what sort of CPU/RAM requirements does it have?


Also while we are at it - Would you recommend using ClamAV as the scanning engine or something like McAfee?

share|improve this question

closed as not constructive by Mark Henderson Jan 16 '12 at 3:55

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

up vote 2 down vote accepted

I've implemented two anti-virus proxy servers using HAVP and ClamAV and it has worked well for the last year or so. Even though HAVP hasn't reached a 1.0 version yet is has been very stable.

If you go the HAVP route, make sure to check out the implementation recommendations located at You will want to make a "Squid sandwich" with a copy of Squid running before and after requests make it to HAVP.

The CPU/RAM requirements aren't that bad since you won't be scanning downloads over a certain size. On a 50 user network we're running HAVP and ClamAV on an older 2.8GHZ Xeon server with 2 GB of RAM with no no problem. There was also no noticeable difference in speed between running Squid alone or with HAVP scanning enabled.

With regards to what scanner(s) to use, I have used ClamAV in mail servers for a long time and it's quite good in that niche. However, the level of protection offered for HTTP clients doesn't seem to be as comprehensive at this time. (But ClamAV is continually getting better so I'm sure that won't be true for long.) We use it as a second level of defense in addition to Sophos on the Windows client boxes and they work very well together.

share|improve this answer

alt text
With this guide I configured Squid + c_icap +Clamav and I found it to be the best atleast for now for squid plus antivirus automatic. It will deny any file with a virus from downloading from internet (of course that clamav detects)

I tried some of the list, like viralator (but seems project dead).

Hope it helps!

share|improve this answer

HAVP uses a multi-process design like Apache to handle many simultaneous requests whilst protecting against memory leaks and faults in the anti-virus scanner libraries or subsystems.

A Squid cache sandwich is best if you require caching, beware these days that most websites are rather public cache unfriendly and such that benefit is only useful for large resources such as youtube videos.

I've gone from Squid sandwich to plain HAVP setup due to the minimal benefit. For example Google update likes running partial range requests which are highly non-conducive to being cached.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.