Open
Bug 1647033
Opened 5 years ago
Updated 1 year ago
Redirects to different subdomains can cause multiple error pages in https only mode
Categories
(Core :: DOM: Security, defect, P3)
Core
DOM: Security
Tracking
()
NEW
People
(Reporter: arthur, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [domsecurity-backlog1])
Attachments
(1 obsolete file)
To reproduce:
- Set dom.security.https_only_mode to true
- go to http://neverssl.com
Results:
- We see an error page for https://neverssl.com/
- After clicking "continue" we then see an error page for https://kbcnhfdlmzrwsvxt.neverssl.com/online
- After clicking "continue" a second time, we see the content of the site.
Expected results:
We should expect to see only one error page.
Possible solution: index the https-only-mode whitelist to eTLD+1.
Updated•5 years ago
|
Severity: -- → S4
Priority: -- → P3
Whiteboard: [domsecurity-backlog1]
Updated•4 years ago
|
Summary: Redirects can cause multiple error messages in https only mode → Redirects to different subdomains can cause multiple error pages in https only mode
Updated•1 years ago
|
Assignee: nobody → mjurgens
Status: NEW → ASSIGNED
Whiteboard: [domsecurity-backlog1] → [domsecurity-active]
Comment 1•1 year ago
|
||
Comment 2•1 year ago
|
||
After talking to Freddy about this again, we have decided to leave this as it is right now, because setting the exceptions to the eTLD+1 would introduce a lot of new problems and edgecases as we would probably still want to keep the per-origin exceptions, and even undesirable behaviour in regards of setting an exception for the whole site, while the user only wants it for the subdomain. Still leaving this open, as those multiple HTTPS-Only error pages are still an annoyance.
Assignee: mjurgens → nobody
Status: ASSIGNED → NEW
Whiteboard: [domsecurity-active] → [domsecurity-backlog1]
Updated•1 year ago
|
Attachment #9352471 -
Attachment is obsolete: true
You need to log in
before you can comment on or make changes to this bug.
Description
•