Why did my request fail with 424 when nothing was wrong with it?
Another operation in the same request failed, and this one depended on it. Find that primary error, usually elsewhere in the Multi-Status response, and fix it.
HTTP 424 FAILED DEPENDENCY
WebDAV: failed because an earlier request in the batch failed. 424 belongs to the 4xx client error class and is defined in RFC 4918.
Loading the workbench.
About HTTP 424
What Does HTTP 424 Failed Dependency Mean?
WebDAV: failed because an earlier request in the batch failed. The code is registered with IANA and defined in RFC 4918.
Client error: the request has a problem, so it cannot be fulfilled as sent. Every code from 400 to 499 shares that general meaning, so a client that does not recognise 424 must treat it like 400.
When Do You See a 424 Response?
424 Failed Dependency comes from WebDAV. It says this part of a request failed only because another action it depended on failed first. You typically see it inside a 207 Multi-Status response, for example during a PROPPATCH that sets several properties atomically: when one property update fails, the others are reported as 424 because the whole set is applied together or not at all.
How Do You Fix a 424?
Clients should look for the entry in the same response that failed with a different code, such as 403 or 409, fix that problem, and resend the whole request. The 424 entries are not errors in their own right. Servers should make sure every 424 can be traced to a primary failure, so clients are not left guessing which operation actually caused it.
What Does a 424 Response Look Like?
HTTP/1.1 424 Failed Dependency
Content-Type: application/xml; charset=utf-8424 is not cacheable by default: a browser or CDN stores it only when Cache-Control or Expires explicitly allows it.
To inspect a real one without sending it anywhere:
- Copy the response headers from your browser Network tab, or from
curl -i. - Paste them into the Header decoder to see every header explained.
- Check caching in the Cache lane.
Which Status Codes Are Related to 424?
- 207 Multi-Status: WebDAV: the body holds separate status codes for several resources.
- 423 Locked: WebDAV: the resource is locked.
- 409 Conflict: The request conflicts with the current state, such as an edit conflict or a duplicate.
Browse every code on the HTTP status codes page.
What Other Lanes Are in the Reference Section?
- HTTP status codes: Every IANA-registered status code, with a page per code.
- MIME types: File extensions to Content-Type, searchable both ways, plus a Content-Type parser.
- HTTP methods: GET, POST, PUT, PATCH, DELETE and the rest: safe, idempotent, cacheable.
Elsewhere in 2http: Header decoder, Cookie decoder, Cache-Control decoder, CORS checker, User-agent parser, and all eleven lanes on the 2http home page. Part of the 2suite.io privacy-first ecosystem.
Frequently Asked Questions
Is 424 used by REST APIs?
Some batch APIs borrow it to mark items skipped because an earlier item failed. Its original definition is in WebDAV, RFC 4918.
Is HTTP 424 an error?
Yes. 424 is a client error response: the problem is in the request, so repeating it unchanged will usually fail again.
Is a 424 response cacheable by default?
No. Caches store a 424 only when Cache-Control or Expires explicitly allows it.
How Can You Verify That Nothing Leaves This Browser?
You do not have to take our word that your headers stay here. Developer tools show every request a page makes, so you can watch this page work and confirm that nothing is sent. The check takes under a minute.
- Open your browser developer tools with
F12, orCmd+Option+Ion a Mac, and select the Network tab. - Reload the page and let it finish. You will see the page's own files, its web fonts, and one anonymous page-view request. Nothing has been typed yet, so none of them can contain your headers.
- Click the clear icon in the Network tab so that the log is empty.
- Paste real headers into any lane and read the result.
- Look at the Network tab again. It is still empty. For extra proof, turn on offline mode after the page loads and every lane keeps working.
Only two things can add a line to that log, and neither carries your headers. Submitting the feedback form sends the vote and comment you typed. Typing characters in a script the page has not displayed yet, such as Cyrillic or Greek, can make the browser fetch the matching font file, and that request names only the font.
2http never sends a request on your behalf: the request builder writes code for you to run, and the meta inspector reads source you paste instead of fetching a URL. The production site also sends a Content-Security-Policy header that tells your browser to refuse connections to anywhere except this site and the anonymous analytics endpoint.