feat(security): allow collection of COOP reports#106565
Merged
Conversation
github-actions
bot
added
the
Scope: Backend
geoffg-sentry
approved these changes
Jan 20, 2026
Contributor
geoffg-sentry
left a comment
geoffg-sentry
left a comment
There was a problem hiding this comment.
Wonderful, thanks oioki!
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Allow setting of COOP header that intends to protect Sentry instances against some cross-origin attacks.
Django provides a native setting
SECURE_CROSS_ORIGIN_OPENER_POLICY(since django/django#14189) but we want to be more flexible with the rollout and also collect violation reports before enforcing the policy.This PR does not change the behavior because
COOP_ENABLED = Falseis set by default.