feat: Content Security Policy: strict-dynamic + (cached) nonce #75
Conversation
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
|
Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch and validate page speed.
Commits
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Porting the out of the box configuration configuration of https://www.aem.live/docs/csp-strict-dynamic-cached-nonce to xWalk.
PR in the aem-boilerplate for reference: adobe#493
Would be very grateful for a more in depth test from the xWalk team with more knowledge. 🙏
I did a basic test to see that UE doesn't break on the authoring side some time ago and saw that the UE author simply rebuilds the HTML and would not take into consideration any CSP, ensuring that nothing breaks, but I don't know if I covered all scenarios.
Test URLs: