acl url_regex on squid3 is not working using an online tested regular expression
I was asked to block Facebook access from 8:00am to 3:00pm for almost all users but them are using **alternative Facebook URLs** to access the social network anyway. This is consuming a lot of our low bandwidth and we can't even work. I decided to design a **regular expression (regex) to parse these URLs and block them**. I don't want to block all facebook URLs but only alternatives. An alternative Facebook URLs mostly contains the words **prod** or **iphone**. The next ones are alternative Facebook URLs registered by our proxy server:
Obviously, the squid3 parser is tagging my acl as **wrong**, but I already tested online and it was good to use. Also it says the acl is empty. What does this mean? The acl was declared with the name **facebook**. I am very confused at this.
Ing. Pedro Pablo Delgado Martell
Participe en el Congreso Internacional de las Ciencias Agropecuarias (AGROCIENCIAS 2017) http://www.agrocienciascuba.com/
> Obviously, the squid3 parser is tagging my acl as **wrong**, but I
> already tested online and it was good to use.
You did not test with the regex library used by your Squid. Different
libraries have different capabilities. The advanced feature (i.e., a
positive lookahead assertion) that your regex is using is apparently not
supported by the library that your Squid is using. Fortunately, that
feature is completely unnecessary for your use case.
> Also it says the acl is empty. What does this mean?
It probably means that after removing bad regexes, there were no regexes
left on the "acl ..." line. You can ignore this warning until you have
no warnings about invalid regular expressions.