Add 'report-uri' directive to Content-Security-Policy - #3112
Merged
Conversation
sethmlarson
force-pushed
the
sentry-csp-report-only
branch
from
September 10, 2026 16:56
367966d to
eec1a92
Compare
JacobCoffee
approved these changes
Sep 11, 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.
Part of #3041, adds the
report-uridirective to theContent-Security-Policy-Report-Onlyheader. This will allow us to set a reporting URL via Sentry and see whether any policies are being violated today before we start enforcement.We don't use
report-toandReporting-Endpointsbecausedjango-cspdoesn't seem to support this as easily? Another thing to do when we move to Django 6.