Closed Bug 1275402 Opened 4 years ago Closed 2 years ago

How should HSTS priming update the mixed-content UI?

Categories

(Core :: DOM: Security, defect, P2)

defect

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?
Blocks: 1246537
Whiteboard: [domsecurity-active]
Blocks: 1313597
Whiteboard: [domsecurity-active] → [domsecurity-active] [hsts-priming]
Duplicate of this bug: 1262263
Priority: -- → P2
No longer blocks: 1313597
Bug 1424917 removed HSTS Priming which renders this bug INVALID.
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.