[squid-users] Best way to deny access to URLs in Squid 3.3.x?

[Rafael Akchurin]

Hello Mirza,

I would humbly propose taking a look at any of the ICAP servers listed on http://www.squid-cache.org/Misc/icap.html.
BTW we are now preparing a native Windows ICAP build of qlproxy and would be glad if you could take a look.

Best regards,
Raf

From: Mirza Dedic <mirza.dedic at outlook.com<mailto:mirza.dedic at outlook.com>>
Date: Tuesday 14 October 2014 19:37
To: "squid-users at lists.squid-cache.org<mailto:squid-users at lists.squid-cache.org>" <squid-users at lists.squid-cache.org<mailto:squid-users at lists.squid-cache.org>>
Subject: [squid-users] Best way to deny access to URLs in Squid 3.3.x?

Just curious, what are some of you doing in your Squid environment as far as URL filtering goes? It seems there are a few options out there.. squidguard... dansguardian.. plain block lists.

What is the best practice to implement some sort of block list into squid? I've found urlblacklist.com that has a pretty good broken down URL block list by category, what would be the best way to go.. use dansguardian with this list or set it up in squid.conf as an "acl dstdomain" and feed in the block list file without calling an external helper application?

Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20141014/8ab780df/attachment.html>