Consider changing LoadInfo::LoadInfo to use IsSecureContext and !IsPotentiallyTrustworthyLoopbackURL
Categories
(Core :: DOM: Security, enhancement, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox117 | --- | fixed |
People
(Reporter: jkt, Assigned: jewilde)
References
Details
(Whiteboard: [domsecurity-active])
Attachments
(1 file, 1 obsolete file)
In LoadInfo::LoadInfo we check for https loadingPrincipals however instead we could check for IsSecureContext and !IsPotentiallyTrustworthyLoopbackURL.
| Reporter | ||
Updated•7 years ago
|
| Reporter | ||
Comment 1•7 years ago
|
||
Comment 2•7 years ago
|
||
There's a r+ patch which didn't land and no activity in this bug for 2 weeks.
:jkt, could you have a look please?
For more information, please visit auto_nag documentation.
| Reporter | ||
Comment 3•6 years ago
|
||
Unassigning, sorry unlikely to get to this. From memory this caused issues / might not be what we want.
Updated•6 years ago
|
Updated•6 years ago
|
Comment 4•4 years ago
|
||
The bug assignee didn't login in Bugzilla in the last 7 months.
:ckerschb, could you have a look please?
For more information, please visit auto_nag documentation.
Hm, something like that would be nice, because we are still using if (mLoadingPrincipal->SchemeIs("https")) { in the loadinfo for detecting if we are in a secure context or not.
Probably we should revisit that if we decide to invest more into mixed content level 2, hence I am marking this bug block Bug 1435733.
| Assignee | ||
Comment 6•3 years ago
|
||
| Assignee | ||
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Comment 8•3 years ago
|
||
| bugherder | ||
Updated•2 years ago
|
Description
•