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?
Inconsistent treatment of 2nd-level domains
-
Guest
Inconsistent treatment of 2nd-level domains
Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20100101 Firefox/17.0
- Giorgio Maone
- Site Admin
- Posts: 9557
- Joined: Wed Mar 18, 2009 11:22 pm
- Location: Palermo - Italy
- Contact:
Re: Inconsistent treatment of 2nd-level domains
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.
In short, if an entry contains only one dot, specifying the protocol is mandatory for matching to work.
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:25.0) Gecko/20100101 Firefox/25.0