Clarify the idempotence stance in the QUERY method proposal. #3341
Conversation
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
Remove the "potentially", to make it clear that it's not safe to consider POST request idempotent, as contrasted to GET and QUERY. What matters in practice is not that a POST request can potentially be idempotent, but that it can potentially not be idempotent. That is, the guarantee, not a hypothesis. Hence the reformulation.
martinthomson
approved these changes
Dec 1, 2025
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.
Remove the "potentially", to make it clear that it's not safe to consider
POSTrequest idempotent, as contrasted toGETandQUERY.What matters in practice is not that a POST request can potentially be idempotent, but that it can potentially not be idempotent. That is, the guarantee, not a hypothesis. Hence the reformulation.