Hi,
I have a url_regex ACL loaded with this file:
https://drive.google.com/file/d/1C5aZqPfMD3qlVP8zvm67c9ZnXUfz-cEW/view?usp=sharing
Then I have an access denial like so:
http_access deny bad_dst_urls
Problem is that I am not expecting to block, eg. https://www.google.com, but I
am.
I know it
> None of the file entries are anchored regex. So any one of them could match.
>> Can anyone please let me know if there's a match, or how to enable debuggingÂ
>> to see which record in this ACL is actually triggering the denial?
>
> To do that we will need to see the complete and exact URL which
Thank you very much.
I will try to set up an external ACL so I don't have to worry about regular
expressions.
Vieri
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users
Regarding the use of an external ACL I quickly implemented a perl script that
"does the job", but it seems to be somewhat sluggish.
This is how it's configured in squid.conf:
external_acl_type bllookup ttl=86400 negative_ttl=86400 children-max=80
children-startup=10 children-idle=3 concurrency=
On 30/09/20 2:27 am, Vieri wrote:
> Hi,
>
> I have a url_regex ACL loaded with this file:
>
> https://drive.google.com/file/d/1C5aZqPfMD3qlVP8zvm67c9ZnXUfz-cEW/view?usp=sharing
>
> Then I have an access denial like so:
>
> http_access deny bad_dst_urls
>
> Problem is that I am not expecting to
Ah. Think I found it.
Line 9600 in the earlier file contains a URL with un-escaped "||"
sequence. Pipe is a reserved character in regex so needs \-escaping like
'?' '*' '.', '$', '^, '[', ']', '(', ')', '$' and '\' in the original URL.
See the note below though for long-term fix ...
On 30/09/2
Of course this script is sluggish since it reads many category files and forks
at least 3-6 times.
If you *really* want to implement this with a perl script, it should read all
files at startup and the script does a lookup using perl data structures.
But I suggest to look at ufdbGuard which is