Cloudflare Redirect Rules Create a Loop Between HTTP and HTTPS

What this guide solves: Visitors are redirected repeatedly after combining origin and edge HTTPS rules. Record the context before changing a server, account or data store. A successful unrelated check does not automatically prove that the complete workflow is healthy.

Recognize this failure and establish a baseline

Inspect Location headers through the entire chain with curl -IL. Record the observed result with its time and environment. If you have multiple sites, service accounts, installations or regions, label them clearly so a working control is not confused with the failing target.

DNS, the CDN edge, TLS termination and the origin are distinct hops. A response that looks correct from one network or cache tier can conceal a rule mismatch or a stale edge copy elsewhere. A precise comparison is usually more informative than clearing caches, restarting every service or changing unrelated permissions. Confirm the reproduction using a harmless sample and preserve the current configuration before editing it.

Three ways to isolate the cause

First safe fix: change one variable

Recommended correction: Choose a single canonical redirect policy with correct proxy HTTPS awareness. Apply it first in a staging environment or on one limited test object when production traffic, orders or private information could be affected. Write down the previous setting and expected result so a rollback is straightforward.

Why not reset everything? Conflicting edge redirect and origin scheme detection may keep bouncing. A broad reset can hide the original cause and create additional failures in permissions, orders, certificates or background jobs. If the proposed correction does not change the exact reproduction test, revert it and move to the advanced inspection instead of stacking speculative fixes.

Advanced diagnosis: inspect the first failing boundary

Check CF SSL mode, trusted forwarded protocol headers and rule precedence. When reading logs, match the same request or transaction across components. A message produced downstream can be secondary to an earlier denial, timeout, incompatible contract or unavailable resource. Use a small known-good request to remove unrelated data from the comparison.

Evidence to keep: Capture the software or protocol version, a masked timestamp, the operation being attempted, the relevant configuration key, and the outcome of the control test. Note both positive and negative findings. If a security rule is involved, preserve the original protection and grant only a narrowly scoped supported exception.

Optional read-only diagnostic

If you have authorized access to the affected host and understand its environment, the following example only inspects state. Replace the example host, service, schema or namespace with your own; it does not repair anything by itself.

curl -IL https://www.example.com/

How to verify the repair

Passing result: HTTP reaches one HTTPS URL without additional cross-scheme hops. Verify the exact operation rather than assuming that an adjacent screen, health endpoint or cached response proves success. Repeat once under normal conditions and check one previously healthy workflow for regressions.

If the result changes only in staging, compare release version, permissions, environment variables and network path with production. If success is intermittent, compare two successive runs and retain the corresponding log evidence before declaring the incident closed.

Safety and rollback

Avoid: Avoid changing many redirect rules simultaneously without a rollback. Store backups, before-and-after settings and sanitized evidence securely. If the action involves orders, identities, databases or customer information, complete an authorized rollback or request maintenance approval before making another production change.

If it still fails

Return to the first comparison: Inspect Location headers through the entire chain with curl -IL. Then investigate the remaining owner: Check CF SSL mode, trusted forwarded protocol headers and rule precedence. Escalate with a concise timeline and the exact point at which expected behavior differs. Do not send passwords, API keys, recovery codes, complete customer records or private signing material to outside support.

Prevent the next occurrence

Version DNS and edge rules, test both authenticated and anonymous paths, and periodically verify TLS and cache behavior from more than one region. Record the minimum regression test for this exact workflow: HTTP reaches one HTTPS URL without additional cross-scheme hops. This is more reliable than applying generic maintenance advice each time a dependency changes.

Official Resources

For the documented interface or feature discussed above, see developers.cloudflare.com official documentation. Confirm that the instructions match your installed product version.