Closed Bug 1678614 Opened 4 years ago Closed 3 years ago

HTTPS-Only Mode and network.trr.mode=3 conflict

Categories

(Core :: Networking: HTTP, defect, P2)

Firefox 83
defect

Tracking

()

RESOLVED FIXED
85 Branch
Tracking Status
firefox85 --- fixed

People

(Reporter: lbotka2, Assigned: kershaw)

References

Details

(Whiteboard: [necko-triaged])

Attachments

(1 file)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:83.0) Gecko/20100101 Firefox/83.0

Steps to reproduce:

connect http://kb.mozillazine.org and http://uu.canna.to/

My 2 Firefox instances work fine (v 83 and v 84.0b3 beta), 2 other instances (v 83 for testing, v 85.0a1 Nightly) produce this error (not found).

I found that network.trr.mode was set differently, and network.trr.mode=3 setting causes this issue, set it to =0.
Then I got the proper “Secure Connection Not Available” error,
clicked Continue to HTTP Site, and set HTTPS_ONLY to OFF on the Lock icon, re-set network.trr.mode=3, and Firefox works fine, opens the HTTP site.

Actual results:

error message:
Hmm. We’re having trouble finding that site. We can’t connect to the server at ....

There is no Lock icon, I can't disable HTTPS-Only for these sites.

Expected results:

error message:
“Secure Connection Not Available”,
"Continue to HTTP Site" possibility

I have to correct, just the opposite
v 83 for testing, v 85.0a1 Nightly work fine, v 83 and v 84.0b3 beta produce this error

Setting a component for this issue in order to get the dev team involved.
If you feel it's an incorrect one please feel free to change it to a more appropriate one.

Component: Untriaged → Networking: HTTP
Product: Firefox → Core

I happened to reproduce this with the latest nightly, so this problem is actually not fixed.
Here is the details of this problem.

  1. We tried to connect to kb.mozillazine.org:443. This failed because server doesn't support 443.
  2. Since trr is enabled, we retry without trr at here.
  3. The trr mode is 3, so AsyncResolveNative immediately returns NS_ERROR_UNKNOWN_HOST, so we can't see the expected error page.
Severity: -- → S4
Priority: -- → P2
Whiteboard: [necko-triaged]
Assignee: nobody → kershaw
Attachment #9189879 - Attachment description: Bug 1678614 - Not replace the previous error code when resolving the host name again → Bug 1678614 - Don't try to resolve the host name again when trr mode is trr only
Pushed by kjang@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/9f21beac8249
Don't try to resolve the host name again when trr mode is trr only r=necko-reviewers,dragana
Attachment #9189879 - Attachment description: Bug 1678614 - Don't try to resolve the host name again when trr mode is trr only → Bug 1678614 - Not replace the previous error code when resolving the host name again
Attachment #9189879 - Attachment description: Bug 1678614 - Not replace the previous error code when resolving the host name again → Bug 1678614 - Don't retry with native DNS if it's trr only mode
Pushed by kjang@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/df97246563c4
Don't retry with native DNS if it's trr only mode r=necko-reviewers,dragana,valentin
Flags: needinfo?(kershaw)
Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 85 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: