HTTP 204 No Content — Success with Empty Body
Informational2xx success
Overview
HTTP 204 No Content indicates the request succeeded but there is no content to return.
Key Details
- Status: 204 No Content
- Category: 2xx Success
- Request was successful
- Response body is intentionally empty
Common Causes
- Successful DELETE request
- PUT/PATCH update with no return data needed
- Form submission that does not need a response body
- Preflight CORS request succeeded
Steps
- 1Do not expect a response body
- 2Update the local state based on the successful request
- 3Check response headers for any relevant metadata
- 4Use for DELETE operations in REST APIs
Tags
http-status2xx-successhttp-204httpstatus-code
More in 2xx Success
http-200-okHTTP 200 OK — What It Means & How to Fix It
Informationalhttp-201-createdHTTP 201 Created — What It Means & How to Fix It
Informationalhttp-202-acceptedHTTP 202 Accepted — What It Means & How to Fix It
Informationalhttp-203-non-authoritative-informationHTTP 203 Non-Authoritative Information — What It Means & How to Fix It
Informationalhttp-204-no-contentHTTP 204 No Content — What It Means & How to Fix It
Informationalhttp-205-reset-contentHTTP 205 Reset Content — What It Means & How to Fix It
InformationalFrequently Asked Questions
No — 204 means success with no body. 404 means resource not found.