Already Reported

Server perspective

Use 208 inside WebDAV multi-status results when a bound resource was already reported earlier in the same response.

When to use

• •Return 208 to reduce duplication in binding-aware DAV responses
• •Use it only when the resource's detailed status was already sent earlier in the same multi-status body

How to respond

• •Make sure the earlier report is complete enough for the client to rely on
• •Keep 208 usage scoped to WebDAV clients that understand the multi-status format

Headers to consider

• •No status-specific header is required; the surrounding 207 multi-status response carries the body contract.

Response body

• •208 appears within the XML multi-status structure rather than as a typical standalone JSON API result

Server-side pitfalls

• •Do not use 208 as a generic 'duplicate item' response for ordinary APIs
• •Do not emit 208 unless the resource really was already reported in the same response

Examples