| Previous | Next |
| HTTP_STATUS_INSUFFICIENT_STORAGE | HTTP_STATUS_BANDWIDTH_LIMIT_EXCEEDED |
HTTP_STATUS_LOOP_DETECTED
A loop can occur during binding traversal, recursive collection processing, redirects, or server-side forwarding. The request cannot complete until the cyclic dependency is removed.
Inspect resource bindings, aliases, redirects, and rewrite rules involved in the request. Capture the request chain instead of increasing recursion limits, which can turn the loop into resource exhaustion.
RFC 5842: Binding Extensions to WebDAV
Operational meaning of HTTP 508 for HTTP_STATUS_LOOP_DETECTED
HTTP 508 (HTTP_STATUS_LOOP_DETECTED) is a server-error response. AllStat records its meaning as “508 Loop Detected”. For HTTP_STATUS_LOOP_DETECTED, interpret it with the request method, selected representation, response headers, and the specification or product that defines the code; the number alone does not prove that application work completed.
Client and server handling for HTTP_STATUS_LOOP_DETECTED
- Correlate HTTP_STATUS_LOOP_DETECTED with origin, gateway, load-balancer, and dependency logs to locate which hop generated it.
- For HTTP_STATUS_LOOP_DETECTED, record request and trace identifiers, upstream timing, retry count, and the health of the selected backend.
- For HTTP_STATUS_LOOP_DETECTED, use bounded retries with backoff only for idempotent work and only when the service policy permits them.
For telemetry, record HTTP 508, method, authority, route template rather than secrets, response headers relevant to caching or retry, latency, upstream identity, and whether the response originated at the application or an intermediary.
Looking for a different code? Search another status or error code.