Reference guide · http-status · Published 2026-08-15 · 3 min read
HTTP 208 Already Reported (WebDAV) explained
Understand HTTP 208 Already Reported, the WebDAV binding status, and why it matters within PROPFIND responses.
- ·What it means
- ·When it is used
- ·Why it matters
The HTTP 208 Already Reported status is a WebDAV detail that almost never appears on a normal website, but it is useful to understand once you read a real WebDAV response. It exists to stop a distributed response from listing the same resource over and over.
What it means
208 Already Reported is defined in RFC 5842, which introduced the WebDAV binding extension. It tells a client that a resource that appears multiple times in a collection was already reported earlier in the same response, so the client should not count it again.
It is a 2xx status, so it means success, and it joins 207 Multi-Status as part of the WebDAV sub-family rather than the everyday web statuses. A real web server serving ordinary pages will not return 208, which is why search-engine-style crawls never meet it.
When it is used
A resource can occur several times within a single WebDAV collection because of bindings, which let multiple URI paths, potentially in different collections, point to the same underlying resource. When a client asks a server to enumerate a collection with PROPFIND on Multi-Status, the result should not repeat the same resource's properties once for every URI that binds to it.
So the server returns a full 207 Multi-Status for the first listing of each resource and a 208 Already Reported for subsequent appearances within the same response. This avoids a huge, redundant document and keeps the client's view of the collection consistent.
A comparison clarifies the two:
| Status | Meaning |
|---|---|
| 207 Multi-Status | The response body carries a D: namespace XML document with per-resource statuses |
| 208 Already Reported | A resource listed earlier in the same Multi-Status is mentioned again without repeating its properties |
Why it matters
For most web work, 208 is background knowledge. It matters in two practical cases:
- If you build or maintain a WebDAV server implementation, you must emit 208 for repeated bindings inside a Multi-Status to avoid double-reporting resources.
- If you write a client that parses Multi-Status, you must handle 208 explicitly rather than treating it as an error, and you must not sum the reported resources as if each entry named a distinct item.
The deeper takeaway is the same as for 207 Multi-Status: the WebDAV family carries its meaning in the response body's propstat elements, and the HTTP status is only the envelope. The HTTP status code list puts 208 in its 2xx context alongside the live-site statuses, and 511 network authentication shows how far the status-code range extends beyond everyday browsing.