27.10.2017 21:33, Antony Stone пишет: > On Friday 27 October 2017 at 17:26:18, Yuri wrote: > >> 27.10.2017 21:17, Antony Stone пишет: >>> On Friday 27 October 2017 at 17:06:01, Yuri wrote: >>>> 27.10.2017 20:55, Alex Rousskov пишет: >>>>> When a regular expression is using extended features, the basic regular >>>>> expression compiler often (or even always?!) does not fail because it >>>>> views the extended features as ordinary plain characters. Thus, Squid >>>>> cannot tell that something went wrong. >>>>> >>>>>> $ echo "foobar" | grep --basic-regexp 'foo|bar' >>>>>> $ echo "foobar" | grep --extended-regexp 'foo|bar' >>>>>> foobar >>>>> As you can see, the basic compiler is silent about the "|" character >>>>> that it does not support. Here is a similar example where a malformed >>>>> >>>>> extended regular expression is silently accepted by the basic compiler: >>>>>> $ echo "foobar" | grep --basic-regexp 'foo(bar' >>>>>> $ echo "foobar" | grep --extended-regexp 'foo(bar' >>>>>> grep: Unmatched ( or \( As for me personally, I would like ECMAScript syntax to be supported in regular expressions of access control lists by default. :) -- ************************** * C++: Bug to the future * **************************
Attachment:
0x3E3743A7.asc
Description: application/pgp-keys
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
