HTTP 201 Created vs 416 Range Not Satisfiable
HTTP 201 (Created) is a 2xx Success response, while 416 (Range Not Satisfiable) is a 4xx Client Error response. 201 indicates that the request succeeded and a new resource was created. Typically returned after POST or PUT requests that create a new entity. In contrast, 416 means that the server cannot serve the requested byte range. The Range header value is outside the resource's size.
Description
The request succeeded and a new resource was created. Typically returned after POST or PUT requests that create a new entity.
When You See It
After successfully creating a new user, post, order, or other resource via a REST API.
How to Fix
No fix needed. Check the Location header for the URL of the new resource.
Description
The server cannot serve the requested byte range. The Range header value is outside the resource's size.
When You See It
When requesting a byte range beyond the file's actual size.
How to Fix
Check the Content-Range in the response for the actual file size and adjust your Range header.
Key Differences
201 is a 2xx Success response, while 416 is a 4xx Client Error response.
HTTP 201: The request succeeded and a new resource was created. Typically returned after POST or PUT requests that create a new entity.
HTTP 416: The server cannot serve the requested byte range. The Range header value is outside the resource's size.
You encounter 201 when after successfully creating a new user, post, order, or other resource via a REST API.
You encounter 416 when when requesting a byte range beyond the file's actual size.
When to Use Which
For 201 (Created): No fix needed. Check the Location header for the URL of the new resource. For 416 (Range Not Satisfiable): Check the Content-Range in the response for the actual file size and adjust your Range header.