nginx: enable Content Security Policies#1909
Merged
Merged
Conversation
added 3 commits
May 23, 2026 11:18
Switch all headers from `Content-Security-Policy-Report-Only` to `Content-Security-Policy`.
lognaturel
approved these changes
May 26, 2026
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
2 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.
Switch all headers from
Content-Security-Policy-Report-OnlytoContent-Security-Policy.What has been done to verify that this works as intended?
Lots of reviewing of CSP reports.
Next step is to enable, and see what breaks in QA.
Why is this the best possible solution? Were any other approaches considered?
It's complicated.
How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?
Should protect them from bad things while allowing normal things. But there's a risk it breaks random functionality for web users.
Does this change require updates to documentation? If so, please file an issue here and include the link below.
No?
Before submitting this PR, please make sure you have:
nextbranch OR only changed documentation/infrastructure (masteris stable and used in production)