[squid-users] Simple REGEX not working...

[David A. Gershman]

Hello again,

After further testing, the looks like the only thing being regex'd 
against is the domain name.  I shrunk the RE down to just:

     acl user_allowed url_regex http  # nothing more, just 'http'

and it /*still*/ failed!!!  It's as if the "whole url" (claimed by the 
docs) is /not/ being compared against.  I'm just posting this here as an 
FYI...no solution has been found. :(

--David

On 7/22/20 7:22 PM, David A. Gershman wrote:
> Hello,
>
> I have the following in my config file:
>
>     acl user_allowed url_regex ^https://example\.com/
>
> but surfing to that site fails (authentication works fine).  My 
> ultimate goal is to have an RE comparable to the PCRE of:
>
>     ^https?:\/\/.*?example\.com\/
>
> While the PCRE works just fine in other tools (my own scripts, online, 
> etc.), I was unable to get it to work within Squid3.  As I stripped 
> away pieces of the RE in the config file, the only RE which seemed to 
> work was:
>
>     example\.com
>
> ...not even having the ending '/'.  However, this obviously does not 
> meet my needs.
>
> I'm on Debian 10 and am unable to determine which RE library Debian 
> compiled Squid3 against (I've got a Tweet out to them to see if they 
> can point me in the right direction).
>
> Ultimately, I would like to get Squid to use PCREs.
>
> Ideas?
>
> Thanks!
>
> --David
>
> _______________________________________________
> squid-users mailing list
> squid-users at lists.squid-cache.org
> http://lists.squid-cache.org/listinfo/squid-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20200722/1fecd140/attachment-0001.html>