Cause a Content-Security-Policy: sandbox header to unregister the Service Worker at that scriptURL.#389
Open
Cause a Content-Security-Policy: sandbox header to unregister the Service Worker at that scriptURL.#389
Conversation
Member
Author
|
@annevk Could you say that on the webappsec thread? It might help push them toward agreeing on some dedicated SW CSP header. |
…vice Worker at that scriptURL. Joshua Peek suggested that this should work (http://lists.w3.org/Archives/Public/public-webappsec/2014Jul/0109.html) because `sandbox` gives the resource a unique origin, which combines with Service Workers' same-origin policy to disallow execution. See w3c#113 and w3c#224.
Contributor
|
Do we have a decision here? |
Member
|
I don't think we have sandboxing for workers yet or decided what that would mean. As far as unregistering goes I think we decided upon something else, no? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Joshua Peek suggested that this should work
(http://lists.w3.org/Archives/Public/public-webappsec/2014Jul/0109.html)
because
sandboxgives the resource a unique origin, which combines withService Workers' same-origin policy to disallow execution.
See #113 and #224.