HTTP 416 Range Not Satisfiable vs 424 Failed Dependency
Both HTTP 416 (Range Not Satisfiable) and 424 (Failed Dependency) belong to the 4xx Client Error category. 416 indicates that the server cannot serve the requested byte range. The Range header value is outside the resource's size. Meanwhile, 424 means that the request failed because it depended on another request that failed (WebDAV).
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.
Description
The request failed because it depended on another request that failed (WebDAV).
When You See It
In batch WebDAV operations when a prerequisite action fails.
How to Fix
Fix the failed dependency first, then retry the operation.
Key Differences
HTTP 416: The server cannot serve the requested byte range. The Range header value is outside the resource's size.
HTTP 424: The request failed because it depended on another request that failed (WebDAV).
You encounter 416 when when requesting a byte range beyond the file's actual size.
You encounter 424 when in batch WebDAV operations when a prerequisite action fails.
When to Use Which
For 416 (Range Not Satisfiable): Check the Content-Range in the response for the actual file size and adjust your Range header. For 424 (Failed Dependency): Fix the failed dependency first, then retry the operation.