What it means
A successful DELETE, or a PUT/PATCH where the client already has the new state. A 204 must not have a body - some clients will error if you send one, and proxies may strip it.
- Class
- 2xx Success
- Defined in
- RFC 9110 §15.3.5
- Cached by default
- Yes, without explicit headers
When you receive a 204
- There is no body to parse. In
fetch, callingresponse.json()on a 204 throws a syntax error, so check the status before reading. - The operation succeeded; the server is telling you there is nothing new to show.
When you send a 204
- Use it for a successful
DELETE, and for aPUTorPATCHwhen you do not return the updated resource. - Send no body at all - not
{}, not an empty string with aContent-Length. - Not for "nothing found": that is 200 with an empty list, or
404when the resource itself is missing.
On the wire
HTTP/1.1 204 No Content Date: Sun, 27 Sep 2026 10:00:00 GMT