-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
And the key difference in these configs is not the ACL contents, but
the ordering in which they are matched.
Mirzas' config starts by telling Squid everything on the LAN/localnet
is allowed. Ok, fine, Squid will do that.
Walters' config will tell
On 15.10.2014 08:13, Amos Jeffries wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
And the key difference in these configs is not the ACL contents, but
the ordering in which they are matched.
Mirzas' config starts by telling Squid everything on the LAN/localnet
is allowed. Ok, fine,
Thanks Walter and Amos, i've taken your advice and now I got the blocking to
partially work. I've re-organized how my ACLs are setup (order) and using your
examples Walter to implement my ACLs.
Working on the facebook example, I have..
acl block_domains_regex dstdom_regex -i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16/10/2014 7:23 a.m., Mirza Dedic wrote:
Thanks Walter and Amos, i've taken your advice and now I got the
blocking to partially work. I've re-organized how my ACLs are setup
(order) and using your examples Walter to implement my ACLs.
Working
acl allow_urls url_regex -i /etc/squid/allowurls-regex-acl.squid (a)
acl block_urls url_regex -i /etc/squid/blockurls-regex-acl.squid (b)
acl allow_urlpaths urlpath_regex -i
/etc/squid/allowurlpaths-regex-acl.squid (c)
acl block_urlpaths urlpath_regex -i
/etc/squid/blockurlpaths-regex-acl.squid
