Closed
Bug 1640853
Opened 4 years ago
Closed 4 years ago
HTTPS Only Mode - Use PermissionManager for Exceptions
Categories
(Core :: DOM: Security, enhancement, P2)
Core
DOM: Security
Tracking
()
RESOLVED
FIXED
mozilla79
Tracking | Status | |
---|---|---|
firefox79 | --- | fixed |
People
(Reporter: julianwels, Assigned: julianwels)
References
(Blocks 1 open bug)
Details
(Whiteboard: [domsecurity-active][tor-P1])
Attachments
(1 file)
We should use nsIPermissionManager
to manage upgrade exceptions for the HTTPS-Only Mode.
- Exceptions should get created through the HTTPS-Only Mode Error Page.
- Exceptions should last for one Session.
Assignee | ||
Comment 1•4 years ago
|
||
Pushed by cbrindusan@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/0a5cf0d822df Using PermissionManager for HTTPS Only Mode upgrade exceptions. r=ckerschb,nhnt11,nika,johannh,necko-reviewers,valentin
Comment 3•4 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox79:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla79
Comment 4•4 years ago
|
||
Hi,
With dom.security.https_only_mode
set to true, I can't find a way to manage exceptions with version 79.
Did I missed something ?
Thanks
Assignee | ||
Comment 5•4 years ago
|
||
Hi antistress!
You can manage exceptions via the Page Info window under the permissions tab. The permission is called 'Use insecure HTTP'.
Is this what you're looking for?
Assignee | ||
Comment 6•4 years ago
|
||
Oops, I'm sorry. I just realized that is coming with version 80 (bug 1644456), my mistake!
Comment 7•4 years ago
|
||
Okay, thanks !
Updated•4 years ago
|
Whiteboard: [domsecurity-active] → [domsecurity-active][tor-P1]
You need to log in
before you can comment on or make changes to this bug.
Description
•