Allow/ignore CSP `upgrade-insecure-requests` on localhost?
Categories
(Core :: DOM: Security, defect, P3)
Tracking
()
People
(Reporter: u611961, Unassigned)
Details
(Keywords: good-first-bug, Whiteboard: [domsecurity-backlog1])
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.75 Safari/537.36
Steps to reproduce:
Set CSP upgrade-insecure-requests
.
Actual results:
No resources loaded on localhost without TLS certificate.
Expected results:
Presuming no security risk; all resources should be loaded as if they were served over HTTPS.
Updated•6 years ago
|
Comment 1•6 years ago
|
||
Since http://localhost/ (and IP address equivs) are supposed to be considered Secure Contexts we shouldn't upgrade them.
Comment 2•6 years ago
|
||
Within NS_ShouldSecureUpgrade in nsNetutil.cpp we could just check for localhost. Or even better, I guess we already have a subroutine within MixedContentBlocker which should provide the carveout we are looking for here as well.
Hi is anyone working on this? I'm new here and would like to contribute
Comment 4•5 years ago
|
||
I cannot reproduce this bug and this looks like it is doing exactly what ckerschb suggested in Comment #2.
Therefore I suggest this bug is marked fixed and closed.
I can't reproduce this bug either.
Comment 6•5 years ago
|
||
This Bug was filed a year ago, probably before jkt fixed it within Bug 1447784, hence marking as duplicate.
Description
•