Remove text on request forgery #369
Merged
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
In looking into this text and the related specifications I decided that it would be better to address the risk of request forgery in the protocol specifications. Right now, they say nothing about this problem, but they really should. I'm going to open an issue. On the assumption that the protocol documents address this problem adequately, then this document doesn't need to concern itself with the problem. It is enough to remove any false claims and defer to the protocol spec. This contains a tweak to the adjacent text for the Origin field (w3c#368), but it doesn't fix that issue. Closes w3c#175.
annevk
reviewed
Oct 13, 2021
vasilvv
approved these changes
Oct 18, 2021
jan-ivar
reviewed
Nov 23, 2021
jan-ivar
reviewed
Nov 23, 2021
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.
In looking into this text and the related specifications I decided that
it would be better to address the risk of request forgery in the
protocol specifications. Right now, they say nothing about this
problem, but they really should. I'm going to open an issue.
On the assumption that the protocol documents address this problem
adequately, then this document doesn't need to concern itself with the
problem. It is enough to remove any false claims and defer to the
protocol spec.
This contains a tweak to the adjacent text for the Origin field (#368),
but it doesn't fix that issue.
Closes #175.
Preview | Diff