[HTTPS-E Rulesets] [HTTPS-Everywhere] In Google.xml, why "[^/@:]"?
Peter Eckersley
pde at eff.org
Tue Jan 18 15:31:59 PST 2011
On Thu, Dec 30, 2010 at 12:00:32AM +0800, Drake, Brian wrote:
> Oh, I didn’t realise that the pattern you object to is being used, in some
> places, to match top-level domains. In those places, yes, that is bad, as it
> could (in theory, at least) match domains that aren’t even controlled by
> Google.
We may have this problem anyway:
http://www.google.co.hk/
>
> While we’re talking about narrowing down the rules, why use clients[0-9]
> when the <target> elements only go from 1 to 5? Isn’t this inefficient (by
> creating more work for the regex engine)?
This is simply historical. It shouldn't have any consequences.
--
Peter Eckersley pde at eff.org
Senior Staff Technologist Tel +1 415 436 9333 x131
Electronic Frontier Foundation Fax +1 415 436 9993
More information about the HTTPS-Everywhere-Rules
mailing list