207 Multi-Status

WebDAV: the XML body contains separate status codes for multiple resources.

207 at a glance

Code: 207
Name: Multi-Status
Class: 2xx Successful
Status: IANA-registered standard code
Defined in: RFC 4918, Section 11.1
Cacheable by default: No by default. Caches store it only when the response carries explicit freshness (Cache-Control max-age, s-maxage or Expires).

What 207 means

207 Multi-Status (RFC 4918) is returned when one request touched several resources, e.g. PROPFIND listing a folder or a COPY of a collection. The real per-resource outcomes are in the multistatus XML body, each with its own status line, so a 207 can contain failures.

What typically causes a 207

WebDAV clients and servers: Nextcloud, ownCloud, SharePoint, macOS Finder and Windows WebDAV mounts, CalDAV and CardDAV sync.

Fix it on the server

Every <response> element must carry its own status; do not report errors only in the top-level code.

Fix it as a client or visitor

Parse the XML and check each <status>; a 207 is not automatically a success.

Headers that go with 207

Header	Role
`Content-Type`	`application/xml` with a DAV:multistatus body.
`DAV`	Advertises WebDAV compliance classes.

Example response

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

<d:multistatus xmlns:d="DAV:"><d:response><d:href>/files/a.txt</d:href><d:propstat><d:status>HTTP/1.1 200 OK</d:status></d:propstat></d:response></d:multistatus>