| 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.
Do not expect a response body
A 204 response ends after the header section and must not contain a message body. Applications can still return metadata such as validators when allowed. Clients should treat success independently from body parsing; code that always expects JSON after every successful request can incorrectly turn a valid 204 into a client-side error.
Looking for a different code? Search another status or error code.