HTTP 100 Continue vs 416 Range Not Satisfiable
HTTP 100 (Continue) is a 1xx Informational response, while 416 (Range Not Satisfiable) is a 4xx Client Error response. 100 indicates that the server has received the request headers and the client should proceed to send the request body. This lets the client know it can continue with the request or abort if the headers were rejected. 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 server has received the request headers and the client should proceed to send the request body. This lets the client know it can continue with the request or abort if the headers were rejected.
When You See It
When a client sends an Expect: 100-continue header, the server responds with 100 before the client sends the body.
How to Fix
This is an interim response — no fix needed. The client should continue sending the request body.
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
100 is a 1xx Informational response, while 416 is a 4xx Client Error response.
HTTP 100: The server has received the request headers and the client should proceed to send the request body. This lets the client know it can continue with the request or abort if the headers were rejected.
HTTP 416: The server cannot serve the requested byte range. The Range header value is outside the resource's size.
You encounter 100 when when a client sends an Expect: 100-continue header, the server responds with 100 before the client sends the body.
You encounter 416 when when requesting a byte range beyond the file's actual size.
When to Use Which
For 100 (Continue): This is an interim response — no fix needed. The client should continue sending the request body. For 416 (Range Not Satisfiable): Check the Content-Range in the response for the actual file size and adjust your Range header.