More
More
208 Already Reported
Used inside a WebDAV Multi-Status response so the same member is not listed twice.
- Code
208- Reason phrase
- Already Reported
- Class
- 2xx Success
- Defined in
- RFC 5842 section 7.1
- Cacheable by default
- No
What it means
Success: the request was received, understood and accepted.
Common causes. WebDAV bindings that make a collection appear more than once.
What to do. Nothing.
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 208 Already Reported Content-Type: text/plain; charset=utf-8 Already Reported
How to send 208
nginx
location /example {
return 208 'Already Reported';
}
PHP
http_response_code(208); echo 'Already Reported'; exit;
Node.js
res.writeHead(208, { 'Content-Type': 'text/plain' });
res.end('Already Reported');
Python (Flask)
# in a view function return 'Already Reported', 208
Change the paths to suit. In nginx, add_header needs always to apply to error responses.
Related codes
- 207Multi-StatusA WebDAV response that carries several separate status codes in its XML body.
- 206Partial ContentThe server is sending only the part of the file the client asked for in its Range header.
- 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.