| Previous | Next |
| HTTP_STATUS_NON_AUTH_INFORMATION | HTTP_STATUS_RESET_CONTENT |
HTTP_STATUS_NO_CONTENT
A 204 response is useful when an action succeeded but the client should remain on the current view, for example after saving settings or deleting a resource. Metadata headers can still describe the updated resource state.
A response to 204 is terminated by the header section and cannot contain a message body. Clients that receive payload bytes after 204 should treat the response as malformed.
Operational meaning of HTTP 204 for HTTP_STATUS_NO_CONTENT
HTTP 204 (this result) is a successful response. AllStat records its meaning as “204 No Content”. Interpret it with the request method, selected representation, response headers, and the specification or product that defines the code; the number alone does not prove that application work completed.
Client and server handling
- Verify what work the response representation says was completed; this result can still describe asynchronous or partial handling.
- use validators, location/status links, and application identifiers supplied by the server.
- do not retry a non-idempotent request merely because the client did not understand the response body.
For telemetry, record HTTP 204, method, authority, route template rather than secrets, response headers relevant to caching or retry, latency, upstream identity, and whether the response originated at the application or an intermediary.
Looking for a different code? Search another status or error code.