Either way would be an improvement of the current state.
I guess, they could even be treated the same (to save me managing even more rules).
Overlap of FQDNs with private relative names will be rare
and if it happens, it should not be too bad either.
Search found 2 matches
- Tue Sep 04, 2018 11:25 am
- Forum: NoScript Development
- Topic: FQDNs handled incorrectly
- Replies: 2
- Views: 4432
- Mon Sep 03, 2018 3:40 pm
- Forum: NoScript Development
- Topic: FQDNs handled incorrectly
- Replies: 2
- Views: 4432
FQDNs handled incorrectly
DNS standards say that proper FQDNs end in a dot (.) to signify the root zone. Other names like foo.bar might or might not be evaluated relative to the local machine's search domain, depending on local configuration. They might give unexpected results after new TLDs like .box or .cloud get delegated...