Redirect Loop Diagnosis

Problem

Visiting the site triggers ERR_TOO_MANY_REDIRECTS or a similar loop and never reaches a stable final page. The issue often comes from multiple redirect rules colliding across the application and network layers.

Symptoms

• Browsers immediately report too many redirects.
• HTTP Check shows repeating URL patterns or repeated protocol switching.
• Users bounce between login pages, locale pages, or www and apex hosts.
• HTTP works, but HTTPS creates the loop.

Top 3 Causes

1. Duplicate HTTPS enforcement - Both the origin and CDN redirect traffic to HTTPS.
2. Host normalization conflict - www, apex, or trailing slash rules disagree across layers.
3. App-state-dependent redirects - Cookies, auth flows, or proxy headers keep sending users back.

Diagnose with DechoNet

• HTTP Check to inspect status codes and Location headers for each hop.
• SSL Check to confirm whether HTTPS enforcement is interacting with TLS problems.
• DNS Lookup to understand which proxy or CDN path the hostname currently follows.

Resolution Checklist

• Identify the two URLs or protocol transitions that repeat in the HTTP Check output.
• Decide whether HTTPS enforcement should live at the CDN or origin, and remove duplication.
• Review www, trailing slash, and locale redirect rules so only one layer owns them.
• Check whether authentication or locale cookies are required and whether the app handles missing cookies safely.
• Re-run HTTP Check and confirm the hop count stabilizes with a valid final response.

When to Escalate

• Escalate to infrastructure operators if CDN rules or managed proxies are outside your access.
• Escalate to the application owner if a CMS, plugin, or SaaS layer generates the loop.
• Escalate to the platform team if proxy header handling such as X-Forwarded-Proto may be wrong.