424 Failed Dependency
A WebDAV response saying the request failed because another action it depended on failed first.
What 424 Failed Dependency means
Mostly seen inside 207 Multi-Status responses. If a PROPPATCH sets several properties and one fails, the rest return 424, because the operation is all or nothing.
Common causes
- One part of a multi-step WebDAV operation failed, so the other parts were not applied.
- A locked or forbidden resource earlier in the same request.
How to fix 424 Failed Dependency
- Look through the 207 body for the status that is not 424. That is the real error.
- Fix that error and send the whole request again.
Example response
HTTP/1.1 424 Failed Dependency
Content-Type: text/plain; charset=utf-8
424 Failed DependencyHow to check for a 424 response
cURL
# Print only the status code
curl -s -o /dev/null -w "%{http_code}\n" https://example.com/JavaScript (Node.js)
const res = await fetch("https://example.com/");
if (res.status === 424) {
console.log(res.status, res.statusText);
}Python
import requests
res = requests.get("https://example.com/")
if res.status_code == 424:
print(res.status_code, res.reason)Go
res, err := http.Get("https://example.com/")
if err != nil {
log.Fatal(err)
}
defer res.Body.Close()
if res.StatusCode == 424 {
fmt.Println(res.Status)
}Specification
424 Failed Dependency is defined in RFC 4918, section 11.4.
Related status codes
- 207
A WebDAV response that carries a separate status code for each of several resources, wrapped in an XML body.
- 423
A WebDAV response saying the file or resource is locked, so the server will not change it until the lock is released.
- 409
The request conflicts with the current state of the resource, such as saving a version that someone else already changed.