-
Notifications
You must be signed in to change notification settings - Fork 149
2015 05 04 SRI Update
Francois Marier edited this page May 4, 2015
·
9 revisions
- Reporting via CSP has been removed but error events are now always triggered.
- Authors can specify more than one hash of the same strength and a sub-resource will be loaded if it matches one of them.
- MIME types are no longer checked and global options have been removed from the metadata format.
- Per-hash options are possible but none will be defined in v1.
- We now require CORS loads or same-origin for a resource to be eligible for integrity checks. The concepts of "publicly cachable and CORS-enabled" are gone from the spec.
From the full list of open issues for v1, these issues need attention:
- Should HTTP headers disqualify resources from getting integrity checked? #305
- Clarify how we handle non-eligible resources and invalid metadata. #317
- Should the
about:
scheme be whitelisted? #319 - Should we mention MIME types in the security considerations? #302
- go through mnot's comments and figure out what we should bring up at the teleconf