Re: [squid-users] Valid ACL-Types for cache_peer_access

Philipp Nyffenegger wrote:
> Hello,
> i'm facing a problem with selective Forwarding in Squid. I'm using
> cache_peer_access to divert different URLs to different Scanning
> Engines. Most of the ACL's are of type "dstdomains". They all work
> fine.
>
> Now my Problem is as follows :
>
> .doubleclick.net is being sent to a URL-Filter which blocks the whole
> .doubleclick.net Domain. Now i would like to have something like
> "http://.*.doubleclick.net/blabla/" being sent towards AV Engine thus
> allowing access to this specific Site/URL.
>
> Whenever i add an url_regex ACL-Type like
> "^http:\/\/.*\.doubleclick.net/blabla$" to a
> "cache_peer_access"-Directive, it's never being redirected
> accordingly. Squid does not complain about wrong ACL-Type used or the
> like.
>

You don't need to escape the backslashes and "$" in a regular expression
matches "end of string". Try ...

^http://(.*\.)?doubleclick\.net/blabla

...instead.

> When i change the ACL-Type to "dstdomain" and add ".doubleclick.net"
> to it, Squid works as expected.
>
> What are the valid ACL-Types working in conjunction with "cache_peer_access" ?
>
> Any help is greatly appreciated.
>
> Kind regards,
> Philipp
>

Chris
Received on Fri Aug 22 2008 - 19:10:03 MDT