Closed
Bug 1275402
Opened 9 years ago
Closed 7 years ago
How should HSTS priming update the mixed-content UI?
Categories
(Core :: DOM: Security, defect, P2)
Core
DOM: Security
Tracking
()
RESOLVED
INVALID
People
(Reporter: kmckinley, Assigned: kmckinley)
References
Details
(Whiteboard: [domsecurity-active] [hsts-priming])
HSTS priming changes the order of operations for mixed-content and HSTS, and delays or even changes the decision of mixed-content. Currently, the mixed-content blcok
This bug should resolve the following:
* How should HSTS priming update the UI when the result of HSTS priming is to upgrade the request?
* What console messages should mixed-content display when it decides to perform HSTS priming?
* What console messages should be displayed when HSTS priming succeeds or fails?
|
||
Updated•9 years ago
|
Whiteboard: [domsecurity-active]
|
Assignee | |
Updated•8 years ago
|
Whiteboard: [domsecurity-active] → [domsecurity-active] [hsts-priming]
|
|
||
Updated•8 years ago
|
Priority: -- → P2
|
|
||
Comment 2•7 years ago
|
||
Bug 1424917 removed HSTS Priming which renders this bug INVALID.
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•