HTTP 508 — Loop Detected
HTTP 508 (WebDAV) stops infinite recursion: while processing the request the server detected a loop in its resource graph — a binding that leads back to itself — and stopped before burning resources forever.
When 508 shows up
- WebDAV collections whose bindings form a cycle.
- Crawler-prone URL graphs that reference themselves transitively.
Mocking a 508 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/tree",
"status": 508,
"delay": 210,
"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 508 mean?
The server detected an infinite loop while processing and terminated the operation. The resource graph, not the request, needs repair.
How can I test a 508 response without a real backend?
Define a mock rule with the method and path your client requests and set the status to 508. The example configuration above returns this response after the listed delay, so the client exercises its 508 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.