I am having problems with my acl, I have the following set:
all Client Address 10.10.1.0/0.0.0.0 allow
manager URL Protocol cache_object deny
localhost Client Address 10.10.1.1/255.255.255.255
127.0.0.1/255.255.255.255 allow
but for some reason others out side the network can use the prox
hi all
i want to create ACL rules that point to files containing the
expressions i want to ban.
for example i want to point my ACL rules to three text files :-
one containing banned ips outside my network
one containing banned URLS outside my network
and one containing ips of clients within my ne
I am a teacher with my own web connection for my classroom. I wish to
have ACL's that deal with my morning class differently than my
afternoon class. I have created the rules and applied them, but they
do not seem to be working. I have cleared my cache and restarted
squid but no luck.
Some Back
> I am having problems with my acl, I have the following set:
> all Client Address 10.10.1.0/0.0.0.0 allow
> manager URL Protocolcache_object deny
> localhost Client Address 10.10.1.1/255.255.255.255
> 127.0.0.1/255.255.255.255 allow
Those are not valid Squid configuration dir
hi all
ok, i've managed to sort this out myself.
looks like it was the syntax of the text files i had created
heres's the solution
i created the two ACL's pointing to different txt files
acl files url_regex -i "/usr/local/squid/etc/banned-files.txt"
acl files url_regex -i "/usr/local/squid/etc/bann
> acl banned-clients src -i "/usr/local/squid/etc/banned-clients.txt"
> banned-clients.txt
> ::
> 146.141.59.230
> 146.141.59.231
> 146.141.59.232
> 146.141.59.233
> 146.141.59.234
> 146.141.59.235
> 146.141.59.236
If you use the src acl type,you have use the subnetmask with that ip-ad
On 21/10/10 02:53, Michael Knichel wrote:
I am a teacher with my own web connection for my classroom. I wish to
have ACL's that deal with my morning class differently than my
afternoon class. I have created the rules and applied them, but they
do not seem to be working. I have cleared my cache
I'm attempting to use ACLs to block non-HTML objects from particular
domains. i.e: users should be able to see the html, but not the images.
Tried various forms of and always end up will all or nothing:
acl suspect-domains dstdom_regex "/etc/squid/suspect-domains.acl"
acl ok-mime-types rep_mime_t
Craig Skinner wrote:
I'm attempting to use ACLs to block non-HTML objects from particular
domains. i.e: users should be able to see the html, but not the images.
Tried various forms of and always end up will all or nothing:
acl suspect-domains dstdom_regex "/etc/squid/suspect-domains.acl"
ple
On Mon, Oct 15, 2007 at 12:04:41AM +1300, Amos Jeffries wrote:
> It should work. What does cache.log / access.log say when (3) is used?
>
Thanks for the help, I'll work on dstdomains next, logs below:
###
acl our_networks src 127.0.0.1/32
http_access allow our_
Craig Skinner wrote:
On Mon, Oct 15, 2007 at 12:04:41AM +1300, Amos Jeffries wrote:
It should work. What does cache.log / access.log say when (3) is used?
Thanks for the help, I'll work on dstdomains next, logs below:
###
acl our_networks src 127.0.0.1/32
h
Craig Skinner wrote:
On Mon, Oct 15, 2007 at 12:04:41AM +1300, Amos Jeffries wrote:
It should work. What does cache.log / access.log say when (3) is used?
Thanks for the help, I'll work on dstdomains next, logs below:
###
acl our_networks src 127.0.0.1/32
h
On Wed, Oct 17, 2007 at 01:12:41AM +1300, Amos Jeffries wrote:
> Doh!. I'm just going to go aside and kick myself a bit.
>
> reP_mime_types is a REPLY acl.
>
> it should be used with http_reply_access :-P
Beautie mate! Stupid of me!
acl our_networks src 127.0.0.1/32
http_access allow our_net
13 matches
Mail list logo
