Closed
Bug 1750551
Opened 3 years ago
Closed 3 years ago
Https-first doesn't upgrade second redirect after upgrading
Categories
(Core :: DOM: Security, defect, P2)
Core
DOM: Security
Tracking
()
RESOLVED
FIXED
People
(Reporter: t.yavor, Assigned: t.yavor)
References
(Blocks 1 open bug)
Details
(Whiteboard: [domsecurity-active])
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
After upgrading a request once, https-first is not upgrading a same-origin redirect to another page because of https://searchfox.org/mozilla-central/source/dom/security/nsHTTPSOnlyUtils.cpp#380. That should be done by the endless loop check and not in that line.
|
Assignee | |
Updated•3 years ago
|
Assignee: nobody → lyavor
|
|
Assignee | |
Updated•3 years ago
|
Summary: Https-first doesn't upgrades same origin redirects → Https-first doesn't upgrades second redirect after upgrading
|
|
Assignee | |
Updated•3 years ago
|
Summary: Https-first doesn't upgrades second redirect after upgrading → Https-first doesn't upgrade second redirect after upgrading
|
||
Updated•3 years ago
|
Severity: -- → S3
Status: NEW → ASSIGNED
Priority: -- → P2
Whiteboard: [domsecurity-active]
|
|
Assignee | |
Comment 1•3 years ago
|
||
|
|
Assignee | |
Comment 2•3 years ago
|
||
|
||
Comment 3•3 years ago
|
||
There's a r+ patch which didn't land and no activity in this bug for 2 weeks.
:lyavor, could you have a look please?
For more information, please visit auto_nag documentation.
Flags: needinfo?(lyavor)
Flags: needinfo?(ckerschb)
|
|
||
Comment 4•3 years ago
|
||
Thanks bot, Tomer is working on a testcase, then we can land it all together...
Flags: needinfo?(lyavor)
Flags: needinfo?(ckerschb)
|
|
Assignee | |
Comment 5•3 years ago
|
||
It is not a real bug since when we remove the line ( which I thought would be more consistent) the result stays the same.
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•