Page 1 of 1

Inconsistent treatment of 2nd-level domains

Posted: Fri Nov 08, 2013 12:36 am
by Guest
When I whitelist a 2nd-level domain, e.g., google.com, NS automatically adds entries for http://google.com and https://google.com.
Whitelisting google.co.uk however just adds google.co.uk. Same goes for blacklisting. What is the reason for this difference?

Re: Inconsistent treatment of 2nd-level domains

Posted: Fri Nov 08, 2013 8:48 am
by Giorgio Maone
Internal weirdnesses in Mozilla's CAPS internal string parsing.
In short, if an entry contains only one dot, specifying the protocol is mandatory for matching to work.