HTTP 208 — Already Reported
HTTP 208 (WebDAV) appears inside multi-status responses to say a member has already been listed earlier in the same report, keeping repeated bindings from appearing twice.
When 208 shows up
- WebDAV PROPFIND depth scans over collections with duplicate bindings.
- Batch reports where the same resource is reachable through several paths.
Mocking a 208 response
A response with this status can be faked end to end with a local mock rule — no backend changes needed. The configuration below mirrors the rule fields the ApiSimul editor uses (method, path, status, delay in milliseconds, response body):
{
"method": "GET",
"path": "/dav/propfind",
"status": 208,
"delay": 260,
"enabled": true,
"body": null
}Dynamic placeholders such as {{random.name}}, {{string.uuid}} or {{number.int 1 100}} can appear inside the body to vary each response, which keeps client-side list rendering and retry logic honest during development.
Frequently asked questions
What does HTTP 208 mean?
Within a multi-status body, this code marks an entry that was already reported in the same response — a de-duplication signal rather than an error.
How can I test a 208 response without a real backend?
Define a mock rule with the method and path your client requests and set the status to 208. The example configuration above returns this response after the listed delay, so the client exercises its 208 handling exactly as it would against a live server.
Related status codes
Need the response in your own project? Spin up rules for any status with the ApiSimul mock server, or browse every status code page.