HTTP 204 No Content vs 226 IM Used
Both HTTP 204 (No Content) and 226 (IM Used) belong to the 2xx Success category. 204 indicates that the server successfully processed the request but is not returning any content. Common for DELETE operations and form submissions that don't need a response body. Meanwhile, 226 means that the server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations.
Description
The server successfully processed the request but is not returning any content. Common for DELETE operations and form submissions that don't need a response body.
When You See It
After DELETE requests, PUT updates where no body is needed, or CORS preflight responses.
How to Fix
No fix needed. The action was successful; there is simply no content to return.
Description
The server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations.
When You See It
When using delta encoding to reduce bandwidth.
How to Fix
Rarely encountered. The response uses Instance Manipulations (IM) as specified.
Key Differences
HTTP 204: The server successfully processed the request but is not returning any content. Common for DELETE operations and form submissions that don't need a response body.
HTTP 226: The server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations.
You encounter 204 when after DELETE requests, PUT updates where no body is needed, or CORS preflight responses.
You encounter 226 when when using delta encoding to reduce bandwidth.
When to Use Which
For 204 (No Content): No fix needed. The action was successful; there is simply no content to return. For 226 (IM Used): Rarely encountered. The response uses Instance Manipulations (IM) as specified.