Closed
Bug 1799662
Opened 2 years ago
Closed 1 year ago
Ensure that Mixed content level 2 upgrade is not triggered if HTTPS-First fallbacks to HTTP
Categories
(Core :: DOM: Security, task, P2)
Core
DOM: Security
Tracking
()
RESOLVED
FIXED
109 Branch
Tracking | Status | |
---|---|---|
firefox109 | --- | fixed |
People
(Reporter: t.yavor, Assigned: t.yavor)
References
(Blocks 1 open bug)
Details
(Whiteboard: [domsecurity-active])
Attachments
(1 file)
Add test case that tests behavior of Mixed content level 2 if https-first is performing a fallback
Assignee | ||
Updated•2 years ago
|
Assignee: nobody → lyavor
Assignee | ||
Comment 1•2 years ago
|
||
Updated•2 years ago
|
Severity: -- → N/A
Priority: -- → P2
Whiteboard: [domsecurity-active]
Pushed by fbraun@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/5cd4375ac1a9 Test https-first performs fallback and mixed content level 2 is not auto upgrading. r=freddyb
Comment 3•1 year ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 1 year ago
status-firefox109:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 109 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•