Closed
Bug 1863286
Opened 1 year ago
Closed 1 year ago
Schemeless HTTPS-First overrides HTTPS-Only in identity pane
Categories
(Core :: DOM: Security, defect)
Core
DOM: Security
Tracking
()
VERIFIED
FIXED
121 Branch
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox119 | --- | unaffected |
firefox120 | --- | wontfix |
firefox121 | --- | verified |
People
(Reporter: maltejur, Assigned: maltejur)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
To reproduce:
- Enable both
dom.security.https_first_schemeless
anddom.security.https_only_mode
- Visit http://https-everywhere.badssl.com/
- Check the identity pane (lock icon)
Expected: We see the HTTPS-Only exception UI
Actually: The HTTPS-Only exception UI is hidden as the identity pane thinks this was a schemeless upgrade
Assignee | ||
Comment 1•1 year ago
|
||
Comment 2•1 year ago
|
||
Set release status flags based on info from the regressing bug 1812192
status-firefox119:
--- → unaffected
status-firefox120:
--- → affected
status-firefox121:
--- → affected
status-firefox-esr115:
--- → unaffected
Pushed by fbraun@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/39e7e0a18465
Schemeless HTTPS-First overrides HTTPS-Only in identity pane r=freddyb
Comment 4•1 year ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 121 Branch
Comment 5•1 year ago
|
||
The patch landed in nightly and beta is affected.
:mjurgens, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- If no, please set
status-firefox120
towontfix
.
For more information, please visit BugBot documentation.
Flags: needinfo?(mjurgens)
Assignee | ||
Updated•1 year ago
|
Flags: needinfo?(mjurgens)
Updated•1 year ago
|
Flags: qe-verify+
Comment 6•1 year ago
|
||
Verified that "Automatically upgrade this site to a secure connection" is not displayed before the fix in Win10x64 using FF build 120.0, but displayed after fix on Win10x64/Mac14 using FF build 121.0b4.
You need to log in
before you can comment on or make changes to this bug.
Description
•