ErrorBase
Independent technical referenceOfficial site
  • Software and systems
  • HTTP service

508

HTTP 508 Loop Detected: the server terminated an operation after finding a loop

Verified with sources2 sourcesReviewed Aug 22, 2026
Technician coming? See what they must show you

Risk level

Low

Usually safe to check without specialist tools.

Urgency

Medium

Quick answer

HTTP 508 means the server terminated the entire operation because it encountered an infinite loop while processing a Depth: infinity request.

Safety first

Stop and check this first

  • Do not recursively delete paths to break an unknown loop. Multiple URIs can bind to the same resource, so path-based deletion can remove unintended data.

Safe checks you can perform

  • Confirm the WebDAV request and Depth field
  • Map collection bindings without following cycles
  • Retry only after correcting the binding graph

Leave these tasks to a qualified professional

  • Do not attempt this professional task: Repair the binding graph and traversal guard

What a technician must be able to justify

A technician is coming

These are the steps they must carry out and show you. Tick them as they work: if steps are skipped, do not accept a part swap.

These are not instructions for opening or handling the equipment yourself. They are the checks that should support a technical conclusion.

  1. Repair the binding graph and traversal guard

    What they doIdentify the cycle by resource identity, correct the responsible binding and confirm loop detection remains enabled.

Before accepting a part or repair

Nothing has been shown yet. Do not accept a part swap based on the code alone.

Checks and evidence, step by step

Follow the documented order. An error code identifies the affected system, but it does not prove by itself which part has failed.

  1. 1

    Confirm the WebDAV request and Depth field

    Tools required

    Procedure

    Verify that 508 came from a binding-aware WebDAV operation using Depth: infinity, not from a browser redirect.

    Do not recursively delete paths to break an unknown loop. Multiple URIs can bind to the same resource, so path-based deletion can remove unintended data.

    Evidence: RFC 5842 section 7.2 - 508 Loop Detected · IANA Hypertext Transfer Protocol Status Code Registry

  2. 2

    Map collection bindings without following cycles

    Tools required

    Procedure

    Use a bounded administrative listing to identify repeated resource identities and the binding that closes the loop.

    Do not recursively delete paths to break an unknown loop. Multiple URIs can bind to the same resource, so path-based deletion can remove unintended data.

    Evidence: RFC 5842 section 7.2 - 508 Loop Detected · IANA Hypertext Transfer Protocol Status Code Registry

  3. 3

    Retry only after correcting the binding graph

    No special tools

    Procedure

    Remove or redesign the unintended cycle, or use a supported bounded operation where it preserves the intended result.

    Do not recursively delete paths to break an unknown loop. Multiple URIs can bind to the same resource, so path-based deletion can remove unintended data.

    Evidence: RFC 5842 section 7.2 - 508 Loop Detected · IANA Hypertext Transfer Protocol Status Code Registry

Where this code applies

A code is meaningful only inside the right product and version context.

Primary scope

System
Software and systems
Brand
HTTP
Product type
HTTP service

Known code variants

  • 508 Boucle détectée
  • 508 Bucle detectado
  • 508 Ciclo rilevato
  • 508 Loop Detected
  • 508 Schleife erkannt
  • código HTTP 508
  • error HTTP 508
  • HTTP 508
  • HTTP error 508
  • HTTP status 508
  • status code 508

What it means

RFC 5842 defines 508 for WebDAV binding loops when the operation cannot continue. It is not a generic label for every application redirect loop.

Warnings and stop conditions

  • Higheditorial warning

    Do not recursively delete paths to break an unknown loop. Multiple URIs can bind to the same resource, so path-based deletion can remove unintended data.

    Evidence: RFC 5842 section 7.2 - 508 Loop Detected · IANA Hypertext Transfer Protocol Status Code Registry

Symptoms and causes

Probable causes · in order

  • WebDAV bindings form a collection cycleConfirmed

    A collection can reach itself through one or more bindings during an infinite-depth traversal.

    Evidence: RFC 5842 section 7.2 - 508 Loop Detected · IANA Hypertext Transfer Protocol Status Code Registry

  • The client requested an unbounded traversalPossible

    Depth: infinity can expose a cycle that a shallower or loop-aware operation would not fully traverse.

    Evidence: RFC 5842 section 7.2 - 508 Loop Detected · IANA Hypertext Transfer Protocol Status Code Registry

Virtual technician

Does 508 still appear after these checks?

Answer a few questions to narrow down the likely cause and the safest next action. Guidance only - it never replaces a professional.

Start diagnosis

Sources and technical references

  1. 1

    RFC 5842 section 7.2 - 508 Loop Detected

    Internet Engineering Task Force · 2010 · official_doc

  2. 2

    IANA Hypertext Transfer Protocol Status Code Registry

    Internet Assigned Numbers Authority · 2025 · official_doc

Sources: RFC 5842 section 7.2 - 508 Loop Detected · IANA Hypertext Transfer Protocol Status Code Registryreviewed 2026-08-22 · verified

Was this entry useful?