HTTP 404 Not Found vs 424 Failed Dependency
Both HTTP 404 (Not Found) and 424 (Failed Dependency) belong to the 4xx Client Error category. 404 indicates that the server cannot find the requested resource. The URL may be wrong, the resource may have been deleted, or it may never have existed. Meanwhile, 424 means that the request failed because it depended on another request that failed (WebDAV).
Description
The server cannot find the requested resource. The URL may be wrong, the resource may have been deleted, or it may never have existed.
When You See It
When a URL is mistyped, a page has been deleted, or an API endpoint doesn't exist.
How to Fix
Verify the URL is correct. Check for typos, case sensitivity, and trailing slashes.
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 404: The server cannot find the requested resource. The URL may be wrong, the resource may have been deleted, or it may never have existed.
HTTP 424: The request failed because it depended on another request that failed (WebDAV).
You encounter 404 when when a URL is mistyped, a page has been deleted, or an API endpoint doesn't exist.
You encounter 424 when in batch WebDAV operations when a prerequisite action fails.
When to Use Which
For 404 (Not Found): Verify the URL is correct. Check for typos, case sensitivity, and trailing slashes. For 424 (Failed Dependency): Fix the failed dependency first, then retry the operation.