More
More
207 Multi-Status
A WebDAV response that carries several separate status codes in its XML body.
- Code
207- Reason phrase
- Multi-Status
- Class
- 2xx Success
- Defined in
- RFC 4918 section 11.1
- Cacheable by default
- No
What it means
Success: the request was received, understood and accepted.
Common causes. WebDAV operations that touch many files at once.
What to do. Read each status in the body; some parts may have failed.
How clients and crawlers treat it
Caching. Not cacheable by default (RFC 9110 section 15.1 does not list it). A cache stores it only when the response says so with Cache-Control or Expires.
Example response
HTTP/1.1 207 Multi-Status Content-Type: application/xml; charset=utf-8 Multi-Status
How to send 207
nginx
location /example {
return 207 'Multi-Status';
}
PHP
http_response_code(207); echo 'Multi-Status'; exit;
Node.js
res.writeHead(207, { 'Content-Type': 'text/plain' });
res.end('Multi-Status');
Python (Flask)
# in a view function return 'Multi-Status', 207
Change the paths to suit. In nginx, add_header needs always to apply to error responses.
Related codes
- 206Partial ContentThe server is sending only the part of the file the client asked for in its Range header.
- 208Already ReportedUsed inside a WebDAV Multi-Status response so the same member is not listed twice.
- 205Reset ContentThe request succeeded and the client should reset the form or view that sent it.
- 204No ContentThe request succeeded and there is deliberately no body.
All status codes · All 2xx codes
Names and numbers from the IANA HTTP Status Code Registry. Google Search behaviour as documented by Google Search Central.