HTTP 204 No Content vs 416 Range Not Satisfiable
HTTP 204 (No Content) is a 2xx Success response, while 416 (Range Not Satisfiable) is a 4xx Client Error response. 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. In contrast, 416 means that the server cannot serve the requested byte range. The Range header value is outside the resource's size.
説明
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.
このコードが表示される場合
After DELETE requests, PUT updates where no body is needed, or CORS preflight responses.
解決方法
No fix needed. The action was successful; there is simply no content to return.
説明
The server cannot serve the requested byte range. The Range header value is outside the resource's size.
このコードが表示される場合
When requesting a byte range beyond the file's actual size.
解決方法
Check the Content-Range in the response for the actual file size and adjust your Range header.
主な違い
204 is a 2xx Success response, while 416 is a 4xx Client Error response.
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 416: The server cannot serve the requested byte range. The Range header value is outside the resource's size.
You encounter 204 when after DELETE requests, PUT updates where no body is needed, or CORS preflight responses.
You encounter 416 when when requesting a byte range beyond the file's actual size.
どちらをいつ使うか
For 204 (No Content): No fix needed. The action was successful; there is simply no content to return. For 416 (Range Not Satisfiable): Check the Content-Range in the response for the actual file size and adjust your Range header.