HTTP 207 — Multi-Status
HTTP 207
Multi-Status
A WebDAV response carrying separate status codes for several resources at once.
What 207 actually means
A single request touched many resources and they did not all end the same way, so the body is an XML document listing a status per resource. Copying a folder where two files succeed and one is locked produces exactly this. The 207 on the outside means "the request was processed"; you have to read the body to find out what actually happened to each item.
Common causes
- A WebDAV PROPFIND listing a collection
- A COPY, MOVE or DELETE across a collection with mixed results
- A CalDAV or CardDAV client syncing multiple items
If you're just trying to view the page
- Nothing directly — the client should be reading the per-item results and showing you which ones failed
- If a WebDAV sync silently misses files, the client is probably ignoring the failures inside a 207
If it's your site
- Always parse the body — treating 207 as a plain success hides the individual failures inside it
- The outer 207 is never an error code; do not map it to a failure state wholesale
Reference
- Status code
- 207
- Reason phrase
- Multi-Status
- Category
- 2xx — Success
- Defined in
- RFC 4918 §11.1
Common questions
- What does HTTP 207 mean?
- A WebDAV response carrying separate status codes for several resources at once. A single request touched many resources and they did not all end the same way, so the body is an XML document listing a status per resource. Copying a folder where two files succeed and one is locked produces exactly this.
- How do I fix a 207 error?
- Nothing directly — the client should be reading the per-item results and showing you which ones failed
- Is 207 a client error or a server error?
- 207 is in the 2xx range, which means success. It is not an error at all.
Related pages
- 200 OK The request worked and the response contains what was asked for.
- 204 No Content The request succeeded and there is deliberately no body to send back.
- 201 Created The request succeeded and a new resource was created as a result.
- 206 Partial Content The server is returning only the requested byte range of a file, not the whole t
- 202 Accepted The request was accepted for processing, but the work has not finished yet.
- 203 Non-Authoritative Information The request succeeded, but an intermediary modified the response on the way.
- 205 Reset Content The request succeeded and the client should clear the form that sent it.
- 208 Already Reported Inside a WebDAV multi-status response, this member was already listed earlier so
- 226 IM Used The server is returning a delta against a copy the client already has, rather th