success RFC 9110
HTTP 204 No Content
Request succeeded but there is no body in the response.
What it means
The server processed the request successfully and there is intentionally no body — either because there's nothing meaningful to return, or because the client should keep displaying the current view. Common for DELETE (nothing to return after deletion) and for PUT/PATCH updates when the client already knows the new state.
When servers send it
- •Successful DELETE — resource is gone, nothing to return
- •PUT/PATCH where the response body would be redundant
- •AJAX endpoints that just record an action (log click, track event)
What the client does
Recognizes success. Does not attempt to parse the (empty) body. Content-Length must be 0.
When you see it
- •Idempotent success — expected
Similar codes
200 OK success
The request succeeded and the response body contains the requested data.
201 Created success
Request succeeded and a new resource was created as a result.
202 Accepted success
Request was accepted for processing but not yet completed.
206 Partial Content success
Server is returning part of a resource due to a Range header from the client.
← All HTTP status codes · HTTP status cheat sheet · HTTP headers reference