[wasm] Use cross origin policy headers #62016
Merged
Conversation
This file contains 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
maraf
added
arch-wasm
|
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsUse xharness arg Fixes #61945
|
pavelsavara
approved these changes
Nov 24, 2021
premun
approved these changes
Nov 24, 2021
This was referenced Nov 24, 2021
|
@maraf could you add a reasoning for the change? @kg had pointed to https://developer.chrome.com/blog/enabling-shared-array-buffer/ , and that would be useful to add to the PR description too. |
|
There is a misalignment between Xharness and Arcade versions. |
maraf
force-pushed
the
CrossOriginPolicy
branch
from
c1586a2
to
18963ef
Compare
This was referenced Nov 29, 2021
ghost
locked as resolved and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Use xharness arg
--web-server-use-copto set cross origin policy headersIn Chrome 92
SharedArrayBufferwas disabled due to a vulnerability. To enable it site must be cross-origin isolated (by COEP and COOP headers). More info at https://developer.chrome.com/blog/enabling-shared-array-buffer/.Fixes #61945