feat: Add support to enable/disable CSP at runtime#10397
Merged
paulbalandan merged 3 commits intoJul 18, 2026
Conversation
memleakd
approved these changes
Jul 9, 2026
michalsn
reviewed
Jul 14, 2026
memleakd
approved these changes
Jul 15, 2026
paulbalandan
approved these changes
Jul 18, 2026
Member
|
Thank you, @patel-vansh |
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.
Description
This PR adds support to let users enable/disable CSP for current request without modifying config variables in runtime.
This lets them exclude specific routes (especially routes handling serving files) from
Content-Security-Policyheader.Checklist: