DoH turned off - Firefox still using Cloudflare
Categories
(Firefox :: Settings UI, defect, P2)
Tracking
()
People
(Reporter: epp, Assigned: valentin)
References
Details
Attachments
(3 files)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:93.0) Gecko/20100101 Firefox/93.0
Steps to reproduce:
DoH is turned off in the Settings, yet on the about:networking page, it indicates it's using DoH via Cloudflare. Screenshots attached.
Actual results:
DoH remains on, despite settings showing it's off.
Expected results:
DoH should remain off, if setting show it's off.
Assignee | ||
Comment 2•4 years ago
|
||
The UI just shows the current TRR URI as parsed from the prefs. I'll add a different label to show the status of the TRR service (enabled/disabled)
Checked bug on Windows10 64bit and MacOs 11 and ubuntu 20.
using Firefox beta 94.0b7, release 93.0 and nightly 95
adding tracking flags.
Assignee | ||
Comment 4•4 years ago
|
||
Just having the TRR URI displayed in about:networking makes it confusing
to people expecting it to be empty when TRR is disabled.
This adds the TRR mode to the page.
Depends on D128888
Comment 6•4 years ago
|
||
bugherder |
Updated•4 years ago
|
I am now using a different Linux distribution which provides Firefox ESR, current version is 91.3.0esr.
I am seeing the same behavior in this release. The DoH box is unchecked, but about:networking is showing it's using Comcast's DoH service. Comcast is my ISP.
Is the fix also going to be included in the next ESR?
Thank you.
Reporter | ||
Comment 10•4 years ago
|
||
This issue is present in Firefox 91.4.0esr. Reopening.
Reporter | ||
Comment 11•4 years ago
|
||
[Tracking Requested - why for this release]:
Comment 12•4 years ago
|
||
Edward, could you navigate to about:config and share the values of the following prefs:
- All prefs that start with "doh-rollout."
- network.trr.mode
- network.trr.uri
Reporter | ||
Comment 13•4 years ago
|
||
doh-rollout.balrog-migration-done true
doh-rollout.clearModeOnShutdown false
doh-rollout.disable-heuristics true
doh-rollout.doneFirstRun true
doh-rollout.doorhanger-decision UIOk
doh-rollout.enabled true
doh-rollout.home-region US
doh-rollout.profileCreationThreshold 1896163212345
doh-rollout.uri https://mozilla.cloudflare-dns.com/dns-query
network.trr.mode 5
network.trr.uri https://mozilla.cloudflare-dns.com/dns-query
Comment 14•4 years ago
|
||
Thanks. Those indicate that DoH is turned off in your profile and we should be running no heuristics, as well as not be using DoH for DNS.
Could you:
- Browse the web a bit, then navigate to about:networking#dns, and check the "TRR" column. You should see "false" on every row.
- Navigate to about:telemetry#events-tab - and if you see any events that have category "doh" and method "evaluate_v2", please share those whole rows here.
Assignee | ||
Comment 16•4 years ago
|
||
Also, since we already landed something for this bug, it should stay closed and we should open a new one for the different issue reported in comment 9.
Reporter | ||
Comment 17•4 years ago
|
||
(In reply to Nihanth Subramanya [:nhnt11] from comment #14)
Thanks. Those indicate that DoH is turned off in your profile and we should be running no heuristics, as well as not be using DoH for DNS.
Could you:
- Browse the web a bit, then navigate to about:networking#dns, and check the "TRR" column. You should see "false" on every row.
- Navigate to about:telemetry#events-tab - and if you see any events that have category "doh" and method "evaluate_v2", please share those whole rows here.
Confirming 'false' listed for every item under TRR.
On about:telemetry#events-tab: it says "Sorry. There is currently no data available in Events"
Assignee | ||
Comment 18•4 years ago
|
||
That means TRR isn't being used.
I'm going to close this for now, since the issue in comment 0 has been resolved.
Please file another bug if you find there's a problem with the fix. Thanks!
Reporter | ||
Comment 19•4 years ago
|
||
(In reply to Valentin Gosu [:valentin] (he/him) from comment #18)
That means TRR isn't being used.
I'm going to close this for now, since the issue in comment 0 has been resolved.
Please file another bug if you find there's a problem with the fix. Thanks!
Bug 1745798 opened for 91esr. Thank you.
Updated•4 years ago
|
Description
•