Redirect loops usually happen when two layers disagree about the canonical URL or protocol, such as the application forcing HTTPS while a proxy reports HTTP, or www and non-www rules conflict.
Common symptoms
- The browser says too many redirects
- The loop began after enabling SSL or CDN
- Only one domain alias is affected
Troubleshooting steps
- Temporarily disable custom redirect rules in
.htaccessand retest. - Confirm the application site URL matches the intended canonical hostname and protocol.
- If a proxy or CDN is used, make sure HTTPS detection is configured correctly at the application layer.
- Avoid stacking redirect rules in the application, CDN, and web config unless each one has a clear purpose.
- Purge caches after changing redirect logic.
Additional notes
- One incorrect forced redirect can loop only on certain aliases while the main domain still works.
- Testing with curl or a redirect checker can reveal which layer is issuing the loop.
When to contact support
Contact support if the loop persists after simplifying to one canonical redirect path.