204 No Content
The server successfully processed the request but is not returning any content. Common for DELETE requests, PATCH operations that don't return the updated resource, or settings updates. The client should stay on the current page — no navigation needed.
What can I do?
- No action needed — this is an informational or success response, not an error.
How to debug & fix
- Do not include a response body with 204 — HTTP spec forbids it
- Use 200 instead if you want to return the updated/deleted resource
- The browser won't navigate on 204 — good for AJAX operations
- Ensure your HTTP client does not attempt to parse a body — 204 forbids one; some clients timeout waiting.
Code Example
app.delete('/users/:id', async (req, res) => {
await User.delete(req.params.id);
res.status(204).end(); // no body
});Related Status Codes
How HTTP Status Codes Work
Every HTTP response carries a three-digit status code that tells the client — browser, API consumer, or search-engine crawler — exactly what happened. The first digit defines the class: 1xx informational (request in progress), 2xx success, 3xx redirection, 4xx client error (bad request, missing auth, not found), and 5xx server failure.
Status codes are standardised in RFC 9110 (HTTP Semantics, 2022). Extensions like WebDAV (RFC 4918) and rate-limit headers (RFC 6585) added codes beyond the core set. When a client receives an unrecognised code, the rule is to treat it as the generic x00 of its class.
Why the Right Code Matters
Semantically correct codes help search engines index accurately (301 passes link equity; 410 removes pages faster than 404), allow API clients to implement correct retry logic (429 + Retry-After, 503 + Retry-After), and let monitoring systems distinguish bugs (500) from load issues (503) from auth failures (401/403).
Looking up a different status code? The full reference covers all HTTP codes with causes, fix guides, and copyable code examples for Node.js and Python.
Browse the full HTTP Status Code reference →