HTTPS-Only exceptions are ignored when set with https:// scheme
Categories
(Core :: DOM: Security, defect, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox117 | --- | fixed |
People
(Reporter: alanhdu, Assigned: maltejur)
References
(Blocks 1 open bug)
Details
(Whiteboard: [domsecurity-active])
Attachments
(3 files, 1 obsolete file)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:99.0) Gecko/20100101 Firefox/99.0
Steps to reproduce:
- Go to a Columbia University webpage (e.g. https://www.columbia.edu/~mh2078/MonteCarlo/MCS_Var_Red_Advanced.pdf)
- Click the lock button disable HTTPS-only mode
- Try to go to the
httpURL
When I visit a Columbia University webpage, I always get redirected to HTTPS which Columbia does not support.
https://www.columbia.edu/~mh2078/MonteCarlo/MCS_Var_Red_Advanced.pdf
Actual results:
No matter what I do, I am always redirected to the https URL, which Columbia does not support (leading to an "Object Not Found" server error). For the life of me I cannot figure out why I'm being redirected to HTTPS in the first place.
Expected results:
After I turn off the HTTPS-only mode, I should stop getting automatically redirected to the HTTP version.
| Comment hidden (duplicate) |
Comment 3•4 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Networking: HTTP' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Comment 4•4 years ago
|
||
FWIW, I can't reproduce this locally.
See the attached file in comment #2, it looks like the pref dom.security.https_only_mode is still true.
Could you go to about:config and check if dom.security.https_only_mode is really false?
Thanks.
Could you go to about:config and check if dom.security.https_only_mode is really false?
Interesting. Yes, if I turn this setting to False, then the bug does not appear. So it looks like the bug is specifically about how exceptions to HTTPS-only mode are handled -- if I set that setting to true but then add an exception for the website (I can do this by either the "Manage Exceptions" page in about:preferences#privacy or by clicking on the lock icon in the URL bar and turning HTTPS-only mode to off for this website), then the exception does not seem to get registered.
Of course, I could totally believe I did something wrong with trying to make an exception for HTTPS-only mode here.
Comment 6•4 years ago
|
||
The severity field is not set for this bug.
:ckerschb, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•4 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
| Assignee | ||
Comment 7•2 years ago
•
|
||
The problem here seems to be that the the exception is only set for https:// www.columbia.edu, since that is the site we are on when setting the exception. But when checking for potential HTTPS-Only exemptions, we are currently checking if http:// www.columbia.edu is excepted.
Possible solutions I see here:
- Always set the exceptions in the identity pane for http, even if the current site is https.
- When checking the exemptions, look for both http and https.
- Save the exemption permissions without the scheme entirely (not sure if that is even possible).
| Assignee | ||
Comment 8•2 years ago
|
||
| Assignee | ||
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
| Assignee | ||
Updated•2 years ago
|
Comment 10•2 years ago
|
||
The severity field for this bug is set to S4. However, the following bug duplicate has higher severity:
- Bug 1714661: S3
:mjurgens, could you consider increasing the severity of this bug to S3?
For more information, please visit BugBot documentation.
| Assignee | ||
Updated•2 years ago
|
Comment 11•2 years ago
|
||
Comment 12•2 years ago
|
||
| bugherder | ||
Description
•