Skip to the content

508 Loop Detected

A WebDAV code: the server found an endless loop while processing the request and stopped. Shared hosting uses the number for something else.

Class
5xx Server error. The request may have been fine, but the server failed to fulfil it.
Defined in
RFC 5842 (WebDAV)

Share this tool:TwitterFacebookLinkedInWhatsAppEmail

What causes it

WebDAV bindings allow a collection to contain itself, directly or by way of another one. A request that has to walk through everything below a folder, with Depth: infinity, would never finish. The server notices, stops and answers 508.

What to do about it

For WebDAV: the request as a whole has failed. Ask for less depth, or have the binding that causes the loop removed.

Most people meet the number somewhere else. Shared hosting that runs CloudLinux answers 508 with the text "Resource Limit Is Reached" when an account has more requests running at once than its plan allows. That has nothing to do with loops. Caching and fewer slow requests help there, or a larger plan.

Not to be confused with

208 Already ReportedHow a server avoids such loops in a listing.
503 Service UnavailableThe more usual code for a server that is out of capacity.

All codes are on the list of HTTP status codes, which can be searched by number and by word.

See all 12