disable caching on integration details endpoint#48728
Merged
Merged
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #48728 +/- ##
==========================================
- Coverage 80.97% 80.96% -0.01%
==========================================
Files 4781 4781
Lines 201897 201908 +11
Branches 11449 11449
==========================================
- Hits 163484 163482 -2
- Misses 38158 38171 +13
Partials 255 255
|
scttcper
approved these changes
May 8, 2023
scttcper
added a commit
that referenced
this pull request
Jun 1, 2023
Adds `referrer-policy: strict-origin-when-cross-origin` to the integration endpoints. Related to #48728 fixes https://getsentry.atlassian.net/browse/WOR-3006
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.
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.
The details and configuration pages of integrations can potentially contain sensitive data. This instructs the client browser to not cache the responses.
This is a best effort at preventing this data from being cached. Browsers will generally honor this, but proxy devices between the client and server are free to ignore the cache header and cache the responses (as they often do).
Ticket: INFO-161