fix: Correct interpretation of SameSite=strict #32824
Closed
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
github-actions
bot
added
Content:HTTP
|
Preview URLs (comment last updated: 2024-07-12 13:42:36) |
|
Thanks for the suggestion! I'm inclined to keep the original here as I think it's more accurate. Even though rel=prerender is deprecated, it's used as an example (of a category of attack*) that |
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
In the Set-Cookie documentation, the explanation for SameSite=Strict is inaccurate.
The specification for SameSite=Strict adds two restrictions base on Lax restriction，but rel=prerender had deprecated，Therefore, there is only one restriction: top-level navigation scene.
Document address：https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-cookie-same-site-00#section-4.1.1
Motivation
Additional details
Related issues and pull requests