208 Already Reported
Used inside a WebDAV 207 response to say a collection's members were already listed earlier, so they are not repeated.
What 208 Already Reported means
Defined by RFC 5842 (WebDAV bindings). When the same resource is reachable through several bindings, 208 stops the server listing its members again and avoids infinite loops on requests with Depth: infinity.
It is meant to appear inside a 207 Multi-Status body, not as the main status of a response.
Example response
HTTP/1.1 208 Already Reported
Content-Type: text/plain; charset=utf-8
208 Already ReportedHow to check for a 208 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 === 208) {
console.log(res.status, res.statusText);
}Python
import requests
res = requests.get("https://example.com/")
if res.status_code == 208:
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 == 208 {
fmt.Println(res.Status)
}Specification
208 Already Reported is defined in RFC 5842, section 7.1.
Related status codes
- 207
A WebDAV response that carries a separate status code for each of several resources, wrapped in an XML body.
- 508
The server stopped a WebDAV request because it found an infinite loop, usually from bindings processed with Depth: infinity.