207 Multi-Status
A WebDAV response that carries a separate status code for each of several resources, wrapped in an XML body.
What 207 Multi-Status means
WebDAV uses 207 when one request touches many resources, such as a PROPFIND on a folder. The body is an XML multistatus document with one response element per resource, each with its own status.
A 207 can mix successes and failures, so clients have to read the body to know what happened.
Example response
HTTP/1.1 207 Multi-Status
Content-Type: text/plain; charset=utf-8
207 Multi-StatusHow to check for a 207 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 === 207) {
console.log(res.status, res.statusText);
}Python
import requests
res = requests.get("https://example.com/")
if res.status_code == 207:
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 == 207 {
fmt.Println(res.Status)
}Specification
207 Multi-Status is defined in RFC 4918, section 11.1.
Related status codes
- 208
Used inside a WebDAV 207 response to say a collection's members were already listed earlier, so they are not repeated.
- 424
A WebDAV response saying the request failed because another action it depended on failed first.
- 200
The request worked. The response body holds the result, such as the page, file or JSON data the client asked for.