HTTP 201 Created vs 204 No Content
Both HTTP 201 (Created) and 204 (No Content) belong to the 2xx Success category. 201 indicates that the request succeeded and a new resource was created. Typically returned after POST or PUT requests that create a new entity. Meanwhile, 204 means 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.
描述
The request succeeded and a new resource was created. Typically returned after POST or PUT requests that create a new entity.
何时出现
After successfully creating a new user, post, order, or other resource via a REST API.
如何修复
No fix needed. Check the Location header for the URL of the new resource.
描述
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.
主要区别
HTTP 201: The request succeeded and a new resource was created. Typically returned after POST or PUT requests that create a new entity.
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.
You encounter 201 when after successfully creating a new user, post, order, or other resource via a REST API.
You encounter 204 when after DELETE requests, PUT updates where no body is needed, or CORS preflight responses.
何时使用哪个
For 201 (Created): No fix needed. Check the Location header for the URL of the new resource. For 204 (No Content): No fix needed. The action was successful; there is simply no content to return.