rch 2000 12:58 AM
>To:[EMAIL PROTECTED]; '[EMAIL PROTECTED]'
>Cc:'debian-user@lists.debian.org'
>Subject: Re: Squid ACLs does not work
>
>At 11:35 AM 3/24/00 +1200, C. Falconer wrote:
>[snip]
>>Squid ACLs are messy and not really intended for fi
;
Subject: Re: Squid ACLs does not work
At 11:35 AM 3/24/00 +1200, C. Falconer wrote:
[snip]
>Squid ACLs are messy and not really intended for filtering based on URLs -
>rather they seem to be for controlling what machines can access your squid
>cache, and which domains your
At 11:35 AM 3/24/00 +1200, C. Falconer wrote:
[snip]
>Squid ACLs are messy and not really intended for filtering based on URLs -
>rather they seem to be for controlling what machines can access your squid
>cache, and which domains your clients get direct (uncached) access to.
I do not agree with
OK, I've tried it on my setup and the answer seems to be that
you have your http_access statements in the wrong order;
try re-arranging this section of squid.conf as follows:
> >> http_access allow manager localhost
> >> http_access deny manager
> >> http_access allow purge localhost
> >> http_acc
Yes, I ran /etc/init.d/squid restart to reload the config file and the
/etc/ban_domains.squid is readable to all, so this should no be a problem.
Sven
On 24-Mar-2000 John Pearson wrote:
> On Thu, Mar 23, 2000 at 11:13:42PM +0100, [EMAIL PROTECTED] wrote
>> Hi,
>>
>> I have some problems with squ
On Thu, Mar 23, 2000 at 11:13:42PM +0100, [EMAIL PROTECTED] wrote
> Hi,
>
> I have some problems with squid and its ACLs.
>
> I'm using Debian 2.2 with Kernel 2.2.13 and squid 2.2STABLE5.
> My ACL section in /etc/squid.conf looks like the following.
>
> acl all src 0.0.0.0/0.0.0.0
> acl manager
Gidday dude. (cc'd to the list because your email address is poked.)
I run squid as the sole cache for a medium sized school network (100 PCs in
an NT domain with a satellite dish at about 400 kbit/s)
We need to censor (or be seen to make an effort to censor) web content.
First we used Cyberp
7 matches
Mail list logo
