HTTP 5xx
508 Loop Detected
The server detected an infinite loop while processing the request.
What causes it
- Circular references, common in WebDAV or misconfigured redirects.
How to fix it
Find and break the circular dependency or redirect loop.
Example response
A typical raw HTTP response a client receives for a 508, with the headers this code is defined around.
HTTP/1.1 508 Loop Detected
Content-Type: text/html; charset=utf-8Related codes
500Common
Internal Server ErrorA generic server-side error. Something failed on the server and it could not complete the request.501
Not ImplementedThe server does not support the functionality required to fulfill the request.502Common
Bad GatewayA server acting as a gateway or proxy got an invalid response from the upstream server it was trying to reach.503Common
Service UnavailableThe server is temporarily unable to handle the request, usually because it is overloaded or down for maintenance.504Common
Gateway TimeoutA gateway or proxy did not get a timely response from the upstream server.505
HTTP Version Not SupportedThe server does not support the HTTP protocol version used in the request.Know before your visitors do.
Sentinel checks your site around the clock from multiple regions and alerts you the moment it starts returning a 5xx error, so you can fix it before it costs you.