vi 4708e7fc8c Avoid the regular expression engine in parsing rule targets. ... I read in the bible (https://www.eff.org/https-everywhere/rulesets) that: """ To cover all of a domain's subdomains, you may want to specify a wildcard target like *.twitter.com. Specifying this type of left-side wildcard matches any host name with .twitter.com as a suffix, e.g. www.twitter.com or urls.api.twitter.com. You can also specify a right-side wildcard like www.google.*. Right-side wildcards, unlike left-side wildcards, apply only one level deep. So if you want to cover all countries you'll generally need to specify www.google.*, www.google.co.*, and www.google.com.* to cover domains like www.google.co.uk or www.google.com.au. """ The previous interpretation is both incorrect (because right wildcards only apply one level deep) and potentially expensive (regular expression matching is exponential in the worst-case.)		2017-12-05 20:54:40 +01:00
..
HTTPSEverywhere/Rules	Avoid the regular expression engine in parsing rule targets.	2017-12-05 20:54:40 +01:00
Text/ICU	Refactored ICU extras.	2015-11-08 17:16:05 +08:00