"Think about it - if you send three DELETE comments/32 requests in a row, it won’t delete three comments. The first successful request will delete the comment with ID 32, and the remaining requests will 404 when they can’t find the already-deleted comment."

Not necessarily. Many implementations return HTTP 204 for any DELETE that succeeds in the sense that the element is gone regardless if it had been there before. To me this always made much more sense than 404.

▲

gbrits 2 days ago | parent [-]

Indeed. Extending idempotency to the response not merely the action wherever possible

	▲	account42 a day ago \| parent [-]
		But why? Now the client has strictly less information than it had before. The client already has the capability to handle 404 for DELETEs.