Closed
Bug 1647829
Opened 5 years ago
Closed 4 years ago
HTTPS Only Mode Error page repeats forever when privacy.firstparty.isolate is enabled
Categories
(Core :: DOM: Security, defect, P3)
Core
DOM: Security
Tracking
()
RESOLVED
FIXED
83 Branch
Tracking | Status | |
---|---|---|
firefox83 | --- | fixed |
People
(Reporter: arthur, Assigned: julianwels)
References
(Blocks 2 open bugs)
Details
(Whiteboard: [domsecurity-backlog1][tor-p1])
Attachments
(1 file)
Steps to reproduce:
- Enable HTTPS Only Mode
- Visit http://jfk.hood.edu/
- The error page is shown. Click "Accept the risk and continue to site"
Actual results:
The error page is show again. Clicking the "Accept" button again and again continues to show the error page; we never reach the content.
Expected results:
The content page should be shown after the user clicks through the error page the first time.
Reporter | ||
Comment 1•5 years ago
•
|
||
It turns out I had privacy.firstparty.isolate enabled when I saw this. It would be nice to fix compatibility with first-party isolation for Tor Browser's sake. (Thanks to Johann for spotting this.)
Assignee | ||
Comment 2•5 years ago
|
||
Oh yeah. I can reproduce that :/
Severity: -- → S4
Priority: -- → P3
Summary: HTTPS Only Mode Error page repeats forever on http://jfk.hood.edu/ → HTTPS Only Mode Error page repeats forever when privacy.firstparty.isolate is enabled
Whiteboard: [domsecurity-backlog1]
Reporter | ||
Updated•4 years ago
|
Whiteboard: [domsecurity-backlog1] → [domsecurity-backlog1][tor-p1]
Updated•4 years ago
|
Blocks: FirstPartyIsolationQA
Assignee | ||
Comment 4•4 years ago
|
||
Assignee | ||
Updated•4 years ago
|
Assignee: nobody → julianwels
Status: NEW → ASSIGNED
Pushed by btara@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/814e24c867db
Fixed HTTPS-Only Mode not working when privacy.firstparty.isolate is enabled r=timhuang
Comment 6•4 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox83:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 83 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•