508 Loop Detected
The server aborted the operation because it detected an infinite loop while processing a request with WebDAV bindings.
At a glance
- Status code
- 508 Loop Detected
- Class
- 5xx, server error, the request looked fine and the server failed
- Defined in
- RFC 5842
- Cacheable by default
- no
- Response body
- Optional.
In detail
A collection that contains a binding back to one of its own ancestors makes a deep traversal endless. 508 is the server refusing to run forever.
Only meaningful for servers that implement WebDAV bindings. It is the failure counterpart of 208 Already Reported.
Find and remove the circular binding. The traversal cannot succeed while it exists.
Examples
HTTP/1.1 508 Loop Detected
Content-Type: text/plain
circular binding in collectionThings that catch people out
- A client retrying a 508 will loop just as hard the second time.
- Some servers exhaust memory before detecting the loop, so a 500 or a dropped connection is the more common symptom.
Try it: HTTP Request Builder
Build a request with any method, headers and body, send it, and read the status line the server returns.
HTTP Request Builder
LOCAL · Browser-OnlyBuild and test HTTP requests with custom headers and body
Authentication
Headers
Generate Code
curl -X GET 'https://api.example.com/endpoint' \
-H 'Content-Type: application/json'Showing a sample URL. Enter your endpoint above to update the snippet.
Related HTTP status codes
All http status codes →208 Already Reported
Inside a WebDAV multi-status response, this member was already listed earlier and its properties are not repeated.
500 Internal Server Error
The server hit an unexpected condition and cannot say anything more specific. It is the catch-all for unhandled exceptions.
507 Insufficient Storage
The server cannot store the representation needed to complete the request, because it is out of space.
510 Not Extended
The server requires further extensions to the request before it will fulfil it. From an experimental extension framework that was never widely adopted.
511 Network Authentication Required
The client must authenticate to gain network access. This is the captive portal code, sent by the network rather than by the site you asked for.
100 Continue
The server has read the request headers, is willing to accept the body, and the client should now send it.
Tools for this
- HTTP Request Builder Free online HTTP request builder - build and test HTTP requests with custom headers and body
- HTTP Headers Checker Free online HTTP headers checker - view HTTP response headers for any URL