The HTTP Status Code 424 means that the client's request failed because it depended on another request that had previously failed.
Frequently Asked Questions
What does the HTTP 424 status code mean?
HTTP 424 Failed Dependency is a client error response indicating that the request failed because it depended on another request that had previously failed. It belongs to the 4xx class of status codes, meaning the problem originates on the client side rather than the server.
When does a server return a 424 status code?
A server returns 424 when it processes requests that must be executed in sequence and a prerequisite request fails, making it impossible to fulfill the dependent request. It is most commonly seen in WebDAV operations and API or microservice architectures where one call relies on the successful outcome of an earlier call.
How do I fix an HTTP 424 error?
Because 424 is a cascading failure, the fix lies in identifying and resolving the root-cause request that failed first — which will often carry a different error code such as 403, 409, or 423. Once that upstream failure is corrected and its request succeeds, the dependent request should no longer return 424.
What is the difference between HTTP 424 and HTTP 400?
HTTP 400 Bad Request is a general-purpose error for a malformed or invalid request, while HTTP 424 Failed Dependency is specific to a situation where the request itself may be well-formed but cannot be completed because a separate prerequisite request did not succeed. Use 424 when the failure is relational, not syntactic.
What is the difference between HTTP 424 and HTTP 428?
HTTP 428 Precondition Required tells the client that the server requires the request to include certain conditions that are missing, whereas HTTP 424 Failed Dependency means the conditions or prerequisite requests were attempted but failed. In short, 428 means a condition was not sent; 424 means a condition was tried and did not succeed.
Is HTTP 424 a client error or a server error?
HTTP 424 is a client error. Its 4xx classification indicates the problem stems from the client's request chain — specifically, that the client issued a request whose success depended on a prior request that the client itself failed to complete successfully. The server is correctly rejecting a request it cannot fulfill given the state of those dependencies.
