user-defined network.trr.excluded-domains may get overwritten
Categories
(Core :: Networking: DNS, defect, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox71 | --- | fixed |
People
(Reporter: nhi, Assigned: kershaw)
References
Details
(Whiteboard: [necko-triaged][trr])
Attachments
(1 file)
From reading the code, and in preparation for bug 1578571, we should make sure that we don't overwrite user-defined values for network.trr.excluded-domains
eg.: https://searchfox.org/mozilla-central/source/netwerk/dns/TRRService.cpp#302
Reporter | ||
Updated•5 years ago
|
Comment 1•5 years ago
|
||
Since we already published the pref on support.mozilla.org I guess we should avoid changing the excluded-domains pref. I think we should add a different pref (builtin-excluded-domains) - that holds localhost, local, and maybe the captive portal domain as well?
Assignee | ||
Comment 2•5 years ago
|
||
(In reply to Nhi Nguyen (:nhi) from comment #0)
From reading the code, and in preparation for bug 1578571, we should make sure that we don't overwrite user-defined values for network.trr.excluded-domains
eg.: https://searchfox.org/mozilla-central/source/netwerk/dns/TRRService.cpp#302
We won't overwrite user-defined values. mExcludedDomains is cleared at here, but we read the preference value from network.trr.excluded-domains again and put the hosts into mExcludedDomains at here.
Valentin, could you take a look at the code regarding mExcludedDomains again? I'm afraid I might get something wrong.
And, do we really need another new pref (builtin-excluded-domains)?
Comment 3•5 years ago
|
||
I think the title may be worded ambiguously.
The worry is that at some point in the future we will want to update trr.excluded-domains
to include other domains (such as the captive portal one maybe). If we change the pref in mozilla-central it will get pushed out to users, and it will overwrite their custom value, which we want to avoid.
What we want to do is to have another pref that we update instead, so we never touch the pref that might be changed by users.
Reporter | ||
Comment 4•5 years ago
|
||
From a UX point of view it is also better to have a different pref for built-in values. Right now we have to explicitly tell users to not delete the values we put there (local, localhost), and only append new values to the list.
Assignee | ||
Comment 5•5 years ago
|
||
Updated•5 years ago
|
Comment 7•5 years ago
|
||
bugherder |
Description
•