HTTP 207 MULTI-STATUS

WebDAV: the body holds separate status codes for several resources. 207 belongs to the 2xx success class and is defined in RFC 4918.

Loading the workbench.

About HTTP 207

What Does HTTP 207 Multi-Status Mean?

WebDAV: the body holds separate status codes for several resources. The code is registered with IANA and defined in RFC 4918.

Success: the request was received, understood, and accepted. Every code from 200 to 299 shares that general meaning, so a client that does not recognise 207 must treat it like 200.

When Do You See a 207 Response?

207 Multi-Status comes from WebDAV (RFC 4918). A single request touched several resources, for example a PROPFIND listing a folder or a DELETE of a collection, and each resource has its own outcome. The body is an XML multistatus document containing one status per resource. You meet it with WebDAV clients and servers such as Nextcloud, SharePoint, macOS Finder network drives, and CalDAV or CardDAV calendar and contact sync.

How Do You Handle a 207?

Clients must parse the XML body and check each inner response; a 207 overall does not mean everything succeeded, and individual entries can be 403, 404, or 423. Servers should return the multistatus document with Content-Type: application/xml and accurate per-resource codes. Outside WebDAV, some APIs borrow 207 for batch endpoints, but a 200 with a JSON array of per-item results is usually clearer.

What Does a 207 Response Look Like?

HTTP/1.1 207 Multi-Status
Content-Type: application/xml; charset=utf-8
DAV: 1, 2

207 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 207?

208 Already Reported: WebDAV: members of this binding were already listed earlier in the response.
424 Failed Dependency: WebDAV: failed because an earlier request in the batch failed.
423 Locked: WebDAV: the resource is locked.

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

Does a 207 mean the whole request succeeded?

Not necessarily. It only says the body holds several separate results. Each resource in the XML has its own status code, and some of them may be errors.

Should a JSON batch API return 207?

It can, but 207 is defined around WebDAV XML. Most JSON APIs return 200 with a per-item status array, which client libraries handle more naturally.

Is HTTP 207 an error?

No. 207 is a success response, not an error.

Is a 207 response cacheable by default?

No. Caches store a 207 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, or Cmd+Option+I on 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.

Was this helpful?