208 Already Reported

WebDAV: members of this binding were already listed earlier in the same multistatus response.

208 at a glance

Code: 208
Name: Already Reported
Class: 2xx Successful
Status: IANA-registered standard code
Defined in: RFC 5842, Section 7.1
Cacheable by default: No by default. Caches store it only when the response carries explicit freshness (Cache-Control max-age, s-maxage or Expires).

What 208 means

208 Already Reported (RFC 5842, WebDAV bindings) appears inside a 207 Multi-Status body. When the same resource is reachable through several bindings, the server reports it once and uses 208 for later occurrences, which keeps recursive PROPFIND from looping or repeating itself.

What typically causes a 208

WebDAV servers that implement bindings (RFC 5842) answering Depth: infinity PROPFIND requests.

Fix it on the server

Only use it inside a DAV:propstat element when the client sent the DAV: bind request header.

Fix it as a client or visitor

Skip entries marked 208; you have already seen the resource earlier in the response.

Headers that go with 208

Header	Role
`DAV`	Client signals support with `DAV: bind`.

Example response

<d:response><d:href>/coll/loop/</d:href><d:status>HTTP/1.1 208 Already Reported</d:status></d:response>