HTTP 508 – Loop Detected
The server detected an infinite loop while processing the request (WebDAV).
Common use case
Triggered by WebDAV operations like COPY or MOVE where a resource is configured to reference itself, creating a processing loop the server refuses to follow forever.
Example
HTTP/1.1 508 Loop Detected
History
Defined in RFC 5842 (2010) as part of WebDAV's BIND extensions.
Did you know?
It plays a similar role to 508's cousin, 999 or "too many redirects" errors in browsers - both exist to stop a client or server from spinning forever on a self-referencing structure.