feat(proxy): [OCISDEV-342] set referrer-policy to no-referrer#11722
Merged
feat(proxy): [OCISDEV-342] set referrer-policy to no-referrer#11722
Conversation
2403905
approved these changes
Oct 8, 2025
bd3d914 to
428f17a
Compare
Contributor
Author
|
Rebased just to sync it with master. No change pushed. |
Change the Referrer-Policy from 'strict-origin-when-cross-origin' to 'no-referrer' to enhance user privacy and security. Previously, the origin was sent on cross-origin requests. This change completely removes the Referrer header from all outgoing requests, preventing any potential leakage of browsing information to third parties. This is a more robust approach to protecting user privacy.
428f17a to
f0b2693
Compare
|
ownclouders
pushed a commit
that referenced
this pull request
Oct 27, 2025
feat(proxy): [OCISDEV-342] set referrer-policy to no-referrer
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.
Description
Change the Referrer-Policy from 'strict-origin-when-cross-origin' to 'no-referrer' to enhance user privacy and security.
Previously, the origin was sent on cross-origin requests. This change completely removes the Referrer header from all outgoing requests, preventing any potential leakage of browsing information to third parties. This is a more robust approach to protecting user privacy.
Motivation and Context
Better privacy.
How Has This Been Tested?
Types of changes