HTTP 100 Continue vs 424 Failed Dependency
HTTP 100 (Continue) is a 1xx Informational response, while 424 (Failed Dependency) 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, 424 means that the request failed because it depended on another request that failed (WebDAV).
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 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
100 is a 1xx Informational response, while 424 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 424: The request failed because it depended on another request that failed (WebDAV).
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 424 when in batch WebDAV operations when a prerequisite action fails.
When to Use Which
For 100 (Continue): This is an interim response — no fix needed. The client should continue sending the request body. For 424 (Failed Dependency): Fix the failed dependency first, then retry the operation.