Summary: | www/squid PCRE regexp doesn't work anymore | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | OlivierW <olivierw1+bugzilla-freebsd> |
Component: | Individual Port(s) | Assignee: | freebsd-ports-bugs (Nobody) <ports-bugs> |
Status: | New --- | ||
Severity: | Affects Only Me | CC: | timp87 |
Priority: | --- | Flags: | bugzilla:
maintainer-feedback?
(timp87) |
Version: | Latest | ||
Hardware: | amd64 | ||
OS: | Any |
Description
OlivierW
2020-01-12 10:11:01 UTC
(In reply to OlivierW from comment #0) Hello, thanks a lot for the report! And sorry for the delay. I'm gonna update squid to 4.10 and try to fix it. Well, to get right answers about --enable-gnuregex it's better to ask squid maillist instead and rise an discussion there. I'm trying to understand how it may be fixed the right way. (In reply to OlivierW from comment #0) Could you share your example of ACL to check it? Hello, Thanks for your answer! I currently don't have access to the specific regexes, but they are similar to: acl example url_regex -i ^http:\/\/www\.example\.com\/.*?\.js I've tried this one in a VM with FreeBSD 12.1 and Squid 4.10 from ports and I am getting the error. I've found I can fix it by removing the lazy quantifier (from .*? to .*): acl example url_regex -i ^http:\/\/www\.example\.com\/.*\.js Both regexes are accepted with Squid 4.10 compiled with "--enable-gnuregex". Maybe I should just change my regexes to remove the lazy quantifier? Hoping it's the only case causing a problem. As you said, I'll ask on Squid's mailing list to know what is the right thing to do. Best Regards, Olivier (In reply to OlivierW from comment #3) Have you got any answer from squid maillist? |