tool::http-status-detail
204 No Content
The server successfully processed the request but returns no content.
Status Code
204
Name
No Content
Category
2xxDetailed Explanation
HTTP 204 No Content indicates that the request was processed successfully but there is no content to return. It is commonly used after DELETE, PUT, or PATCH requests when the server wants to signal success without sending a response body. Browsers receiving a 204 stay on the current page and do not redirect.
Common Causes
- ▸A DELETE request successfully removed a resource
- ▸A PUT/PATCH request updated a resource but no response body is returned
- ▸A CORS OPTIONS preflight response
- ▸A form submission where the current page state should be preserved
How to Fix
- 1.204 is a normal response — no fix needed
- 2.If a response body is required, use 200 OK instead
- 3.If the newly created resource details are needed, use 201 Created
- 4.Never include a body in a 204 response (HTTP spec violation)
Related HTTP Headers
Cache-ControlETagResponse Example
HTTP/1.1 204 No Content Cache-Control: no-cache
Related Status Codes
200OKThe request has succeeded.→201CreatedThe request has been fulfilled and a new resource has been created.→202AcceptedThe request has been accepted but not yet acted upon.→203Non-Authoritative InformationThe response is from a transforming proxy, not the origin server.→205Reset ContentThe server processed the request; the client should reset the document view.→
ad · 300×250
// related tools