Re: [squid-users] Blacklist Service for Squid Proxy - Squidblacklist.org

From: Eliezer Croitoru <eliezer_at_ngtech.co.il>
Date: Tue, 19 Mar 2013 19:02:30 +0200

This is the place to get help.
Don't hesitate to just ask.

Eliezer

On 3/19/2013 9:27 AM, Squidblacklist wrote:
> Scratch that, nothing wrong with -i in the directive, It appears my
> test environment has developed a routing issue directing packets to the
> squid proxy, I apologize for the wasted messages
>
>
>
> Signed,
>
> Fix Nichols
>
> http://squidblacklist.org
>
>
> On Tue, 19 Mar 2013 20:22:15 +1300
> Amos Jeffries <squid3_at_treenet.co.nz> wrote:
>
>> On 19/03/2013 8:07 p.m., Squidblacklist wrote:
>>> Sir, if I do as you suggest and insert a -i
>>>
>>> refresh_pattern ^ftp: 1440 20% 10080
>>> refresh_pattern ^gopher: 1440 0% 1440
>>> refresh_pattern (/cgi-bin/|\?) 0 0% 0
>>> refresh_pattern . 0 20% 4320
>>>
>>>
>>> the blacklist acls' only work half the time with the -i inserted,
>>> do you have any suggestions for a solution? In the meantime I am
>>> leaving -i out of the directive to retain functionality of the
>>> blacklists
>>
>> Very strange. All it does is make the regex pattern match
>> case-insensitive. Nothing related to ACLs.
>>
>> I am talking about:
>> refresh_pattern -i (/cgi-bin/|\?) 0 0% 0
>>
>> as per: http://www.squid-cache.org/Doc/config/refresh_pattern/
>>
>> Amos
>>
>
Received on Tue Mar 19 2013 - 17:03:17 MDT

This archive was generated by hypermail 2.2.0 : Tue Mar 19 2013 - 12:00:06 MDT