improve the example for no-referrer-when-downgrade policy #35997
Conversation
This file contains 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
…ade referrer-policy https://w3c.github.io/webappsec-referrer-policy/#referrer-policy-no-referrer-when-downgrade the specification allows Referer header to be added when the referrer-URL is a non-potentially trustworthy URL, regardless of the potential trustworthiness of referred-URL
…wngrade-add-example
Thilak-KN
requested review from
hamishwillee
and removed request for
a team
github-actions
bot
added
Content:HTTP
|
Preview URLs (comment last updated: 2024-09-30 04:37:38) |
…owngrade-add-example
hamishwillee
approved these changes
Sep 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Improves the example for
no-referrer-when-downgradereferrer-policy.Motivation
I was trying out examples given in the MDN docs, and wondered what happens if an HTTP page references a resource served over HTTPS/HTTP
Additional details
W3C webappsec-referrer-policy says, in case of
no-referrer-when-downgradepolicy, therefererheader is added to the request if referrer-URL is a non-potentially trustworthy URL, regardless of the potential trustworthiness of referred-URLI tested the following snippet to verify it from my local system
Related issues and pull requests