-
Notifications
You must be signed in to change notification settings - Fork 76
Integrity-Policy
header for scripts
#1173
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.
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
Comments
cc @mozfreddyb |
And forwarding to @beurdouche and @tomrittervg 😉 |
We have been thinking about and discussing this, we'd like to talk more on the upcoming call. :) |
Integrity-Policy
header for scripts
Edited the title and description to reflect the latest thinking on this, as discussed with @mozfreddyb & @tomrittervg |
We are positive about this as this is the first milestone towards an improved Web Application Integrity Consistency and Transparency mechanism for the Web. |
Uh oh!
There was an error while loading. Please reload this page.
Request for Mozilla Position on an Emerging Web Specification
Integrity-Policy
header for scriptsIntegrity-Policy
header for scripts WebKit/standards-positions#458Other information
Subresource-Integrity (SRI) enables developers to make sure the assets they intend to load are indeed the assets they are loading. But there's no current way for developers to be sure that all of their scripts are validated using SRI.
The Integrity-Policy header gives developers the ability to assert that every resource of a given type needs to be integrity-checked. If a resource of that type is attempted to be loaded without integrity metadata, that attempt will fail and trigger a violation report.
This is a revival of CSP's
require-sri-for
The text was updated successfully, but these errors were encountered: