Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Content-Security-Policy: block-all-mixed-content #3699

Closed
Androbin opened this issue Sep 2, 2017 · 2 comments
Closed

Content-Security-Policy: block-all-mixed-content #3699

Androbin opened this issue Sep 2, 2017 · 2 comments
Labels
Support data suggestion

Comments

@Androbin
Copy link

Androbin commented Sep 2, 2017

I wanted to compare the support for the Content-Security-Policy header directives upgrade-insecure-requests and block-all-mixed-content.

The former is listed here: https://caniuse.com/#feat=upgradeinsecurerequests
But the latter I could not find.
@cvrebert
Copy link
Contributor

@Schweinepriester
Copy link
Contributor

Available via MDN now: https://caniuse.com/?search=block-all-mixed-content

(upgrade-insecure-requests also has additional entries via MDN: https://caniuse.com/?search=upgrade-insecure-requests)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Support data suggestion
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@cvrebert @Fyrd @Schweinepriester @Androbin