The loop is usually stored in a cookie, so Chrome keeps redirecting even after the server-side rule is fixed.
The loop is usually stored in a cookie, so Chrome keeps redirecting even after the server-side rule is fixed.
Click the padlock → Cookies and site data → Manage on-device data → Delete the domain's cookies, then reload. If a fresh incognito window works, cookies were the cause.
Chrome has its own failure mode, but ERR_TOO_MANY_REDIRECTS has a wider set of causes. The most common one overall is: The CDN forwards to the origin over HTTP while the origin redirects all HTTP to HTTPS — an infinite loop.
Switch the CDN's SSL mode to Full so the origin leg is encrypted, or make the origin trust the forwarded-proto header instead of the raw scheme.
The uptime probe returns the full redirect chain, so you can see the exact two URLs bouncing off each other instead of inferring it from behaviour.
The loop is usually stored in a cookie, so Chrome keeps redirecting even after the server-side rule is fixed.
Click the padlock → Cookies and site data → Manage on-device data → Delete the domain's cookies, then reload. If a fresh incognito window works, cookies were the cause.
Two rules are bouncing the request back and forth — most often an HTTPS redirect at the application level fighting a proxy that is forwarding as plain HTTP, so each side thinks the other needs to upgrade.