HTTP 204 – No Content
The request succeeded but there is no content to send back, and the client should keep its current view.
Common use case
Standard response for successful DELETE requests, or PUT/PATCH calls where the client already has the updated state and doesn't need it echoed back.
Example
HTTP/1.1 204 No Content
History
Defined in HTTP/1.0 (RFC 1945, 1996).
Did you know?
A 204 response must not include a message body - some HTTP clients will throw an error if a server mistakenly sends one anyway.