Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify that request bodies on DELETE are not interoperable #300

Merged
merged 2 commits into from
Feb 4, 2020
Merged

Clarify that request bodies on DELETE are not interoperable #300

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
bfc79b8
Clarify that request bodies on DELETE are not interoperable
mnot Feb 3, 2020
4972b14
trim reasoning
mnot Feb 4, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
trim reasoning
  • Loading branch information
@mnot
mnot committed Feb 4, 2020
commit 4972b14de42f75867e38d23b84303c0e04dc46cd
3 changes: 1 addition & 2 deletions draft-ietf-httpbis-semantics-latest.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4685,8 +4685,7 @@ Content-Range: exampleunit 11.2-14.3/25
A client &SHOULD-NOT; generate a body in a DELETE request. A payload
received in a DELETE request has no defined semantics, cannot alter the
meaning or target of the request, and might lead some implementations to
reject the request and close the connection because of its potential as a
request smuggling attack (<xref target="request.smuggling"/>).
reject the request.
</t>
<t>
Responses to the DELETE method are not cacheable. If a successful DELETE
Expand Down