-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add cross-origin-resource-policy response header #2394
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It also would be great to add a test (an integration test) to make sure the relay responds with the correct headers.
@olksdr Thank you for the suggestion. I wasn't too sure where to add them, but I was able to track down where the other CORS headers are tested as well. Please let me know if the added test is sufficient. :) |
Co-authored-by: Oleksandr <1931331+olksdr@users.noreply.github.com>
Co-authored-by: Oleksandr <1931331+olksdr@users.noreply.github.com>
Co-authored-by: Oleksandr <1931331+olksdr@users.noreply.github.com>
a5bf519
to
0d6d9e0
Compare
Fix for getsentry/sentry#41225.
Browsers are starting to require the CORP header it seems. Relay sets
Access-Control-Allow-Origin: *
, but this is not sufficient for those that have stricter headers set:tower_http
's CORS module does not support CORP/COOP/COEP so I just added the static header on the response.