Add support for Content-Security-Policy's "upgrade-insecure-requests" meta tag
See original GitHub issueCurrently adding the Content Security meta tag to upgrade insecure requests…
<meta http-equiv="Content-Security-Policy" content="upgrade-insecure-requests">
results in the error message…
The attribute 'http-equiv' may not appear in tag 'meta name= and content='.
Can we add support for it?
(CC: @mikewest, @cramforce)
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
CSP: upgrade-insecure-requests - HTTP - MDN Web Docs
The HTTP Content-Security-Policy (CSP) upgrade-insecure-requests directive instructs user agents to treat all of a site's insecure URLs ...
Read more >Upgrade Insecure Requests
Upgrade Insecure Requests essentially means that any page resource being called from a non-secure source (http) should be changed to a secure source...
Read more >How can I allow Mixed contents (http with https) using ...
2 Answers 2 · You can use it to automatically upgrade http request to https (though browser support isn't universal). · You can...
Read more >Fixing mixed content - web.dev
The upgrade-insecure-requests CSP directive instructs the browser to upgrade insecure URLs before making network requests.
Read more >Upgrade Insecure Requests Sample - GitHub Pages
The "Upgrade Insecure Requests" Content Security Policy can be used to automatically upgrade insecure (e.g. http: ) requests to a secure alternative (e.g. ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hmm, I’m certainly not opposed to doing this. @Gregable
I have stopped caring personally, but it still sounds like a good feature to support. So, stale 🤖, keep this open, please.