Re: [squid-users] "url_rewrite_access"-directive bypasses everything

From: Tom Tux <tomtux80_at_gmail.com>
Date: Fri, 25 Jun 2010 07:22:55 +0200

This seems not to work.

I have the following directive:
acl ALLOWED_HOSTS src "/etc/squid/Allowed_hosts"
url_rewrite_access deny ALLOWED_HOSTS
url_rewrite_access allow all

In the file "/etc/squid/Allowed_hosts" I have the following entry:
10.xx.xx.xx/32

But on the Redirector-Logfile, I can see, that websites, called from
the host listed in the file "Allowed_hosts", are blocked. So this host
isn't bypassing the redirector.
Thanks.
Tom

2010/6/24 Amos Jeffries <squid3_at_treenet.co.nz>:
> Tom Tux wrote:
>>
>> Hi
>>
>> With the following acl
>>
>> acl ALLOWED_HOSTS src "/etc/squid/Allowed_hosts"
>>
>> I set a list of hosts, which should be able, to get webaccess without
>> passing the url_rewrite_program. I read, that I can use the
>> "url_rewrite_access"-directive to make a kind of bypassing the
>> redirector.
>>
>> How do I have to understand the url_rewrite_access-directive? Does
>> "deny" mean, that the host passes or bypasses the redirector?
>>
>> I set the directive like this:
>> url_rewrite_access allow ALLOWED_HOSTS
>> With that, the Hosts listed in the file "/etc/squid/Allowed_hosts" are
>> allowed to get internet-access. But, other clients can now access
>> websites, which should normally blocked. It seems, that the
>> url_rewrite_access-directive bypasses now all requests.
>>
>> Is there an explanation for this behavior?
>
> url_rewrite_access does neither permit nor deny access to websites.
>
> It determines which requested URL get sent to the url_rewrite_program for
> alteration before being passed on.
>
> Your first instinct was correct to set:
>  url_rewrite_access deny ALLOWED_HOSTS
>  url_rewrite_Access allow all
>
> Amos
> --
> Please be using
>  Current Stable Squid 2.7.STABLE9 or 3.1.4
>
Received on Fri Jun 25 2010 - 05:23:03 MDT

This archive was generated by hypermail 2.2.0 : Fri Jun 25 2010 - 12:00:04 MDT