Runs in your browser. Your files and text never leave your device - nothing is uploaded.
5xx Server Error
What it means
The server detected an infinite loop while processing the request (WebDAV).
| Property | Detail |
|---|---|
| Status class | 5xx Server Error |
| Defined in | RFC 5842, Section 7.2 — RFC 5842 is an Experimental RFC that defines WebDAV bindings, which let one resource appear at several paths. |
| Cacheable by default | Only with explicit caching headers: a cache stores it when the response carries Cache-Control (max-age, s-maxage or public) or Expires. |
| Who needs to act | The server or hosting account owner. |
What does HTTP 508 Loop Detected mean?
HTTP 508 Loop Detected means the server stopped an operation because it found an infinite loop while processing a WebDAV request with Depth: infinity, and the whole operation failed. It is defined by RFC 5842 for WebDAV bindings. Some shared hosts also show 508 when an account exceeds its resource limits, a different, non-standard use.
How 508 Loop Detected works
WebDAV bindings let the same collection appear at more than one path, so a collection can end up containing a binding to itself or to one of its parents. A PROPFIND, COPY or similar request with Depth: infinity would then walk the tree forever. RFC 5842 lets the server detect this and fail the whole operation with 508. On ordinary websites, a 508 is far more likely to come from shared hosting: hosts running CloudLinux show '508 Resource Limit Is Reached' when an account exceeds its CPU, memory or concurrent-process limits. That message has nothing to do with WebDAV.
Example 508 request and response
PROPFIND /shared/ HTTP/1.1
Host: dav.example.com
Depth: infinity
HTTP/1.1 508 Loop Detected
Content-Type: application/xmlA binding inside /shared/ points back to an ancestor, so a full-depth listing would never end. The server stops and reports the loop.
What causes a 508 Loop Detected
- A WebDAV collection containing a binding to itself or an ancestor, traversed with Depth: infinity.
- Shared hosting accounts hitting their entry-process, CPU or memory limits, shown as '508 Resource Limit Is Reached'.
- Traffic spikes, aggressive bots or slow scripts holding many processes open on a small hosting plan.
How to fix a 508 Loop Detected
If you use WebDAV
- Request a limited depth, such as Depth: 1, and walk the tree level by level.
- Find and remove bindings that point back to a parent collection.
If your host shows '508 Resource Limit Is Reached'
- Open your hosting panel's resource usage page to see which limit was hit.
- Block abusive bots, enable page caching, and fix slow plugins or scripts that hold processes open.
- Upgrade the plan if legitimate traffic needs more concurrent processes.
Related status codes
- 503 Service Unavailable: A temporary overload of the service as a whole.
- 507 Insufficient Storage: Another WebDAV-derived 5xx code, for running out of storage.
- 429 Too Many Requests: The standard way to tell one client that it is sending too much.
Frequently asked questions
The server detected an infinite loop while processing the request (WebDAV).
A WebDAV collection that contains a binding to itself or a parent, traversed with "Depth: infinity". Some shared hosts also show 508 when an account hits its resource limits.
For WebDAV, remove the looping binding or request a limited depth. On shared hosting, reduce resource usage or upgrade the plan.
No. Browsers detect redirect loops themselves, for example showing ERR_TOO_MANY_REDIRECTS in Chrome, while the server keeps returning ordinary 301 or 302 responses. A 508 is only for loops the server detects while processing a WebDAV request.
Sources
Other 5xx Server Error codes
Reviewed by Raja Jahangir · Last reviewed: October 7, 2026