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.

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

SRI: Fail open on ineligible #394

Merged
merged 3 commits into from Jun 6, 2015

Conversation

metromoxie
Copy link
Contributor

As per the discussion in #317, I believe that ineligible resources should fail open, not closed. More specifically, since a CORS failure because of a lack of CORS headers from the server will result in a network error (and thus SRI will never be activated), this has the practical effect that if a developer forgets to add the crossorigin attribute, the integrity should not be enforced. Thoughts @devd @mozfreddyb @fmarier?

@metromoxie metromoxie added the SRI label Jun 5, 2015
@metromoxie metromoxie self-assigned this Jun 5, 2015
@metromoxie metromoxie force-pushed the sri-ineligible-should-fail-open branch from 269bb45 to 3a62289 Compare June 5, 2015 19:17
@fmarier
Copy link
Member

fmarier commented Jun 6, 2015

Now that eligibility is down to just checking for CORS or same-origin, I think this makes sense.

@metromoxie
Copy link
Contributor Author

Okay, I'm going to merge, since @fmarier and @devd seem to agree. @mozfreddyb, feel free to jump in if you have a different perspective.

metromoxie added a commit that referenced this pull request Jun 6, 2015
@metromoxie metromoxie merged commit ef378bb into w3c:master Jun 6, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants