Closed
Bug 1703216
Opened 4 years ago
Closed 4 years ago
Get rid of network.trr.bootstrapAddress pref
Categories
(Core :: Networking: DNS, task, P2)
Core
Networking: DNS
Tracking
()
RESOLVED
FIXED
89 Branch
| Tracking | Status | |
|---|---|---|
| firefox89 | --- | fixed |
People
(Reporter: valentin, Assigned: valentin)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged])
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
Bug 1700378 comment 11 is an example of a situation that has occurred more than once: people setting the bootstrapAddress pref then changing the provider URI.
In order to improve the situation here I propose the following:
- remove the network.trr.bootstrapAddress pref from all.js - this would make the pref inaccessible so users don't fiddle with it by mistake, and so it's ignored for users who already have it.
- Use a different pref name to achieve the same: network.trr.bootstrapAddr. We only use it in tests, and don't add it to all.js to make it less accessible.
- Optional follow-up: have a mechanism that resets the bootstrapAddr when changing the URI pref.
|
Assignee | |
Comment 1•4 years ago
|
||
Depends on D109723
|
||
Comment 2•4 years ago
|
||
Should we consider another follow-up where we fall-back to native DNS for bootstrap if the user-set bootstrap address wasn't helpful?
|
|
Assignee | |
Comment 3•4 years ago
|
||
I guess we could, but I'm not sure it's worth the complexity just yet.
Pushed by valentin.gosu@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/52be5dfc63af
Get rid of network.trr.bootstrapAddress pref r=nhnt11
|
||
Comment 5•4 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 4 years ago
status-firefox89:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 89 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•