Nginx Redirect Loop Fix

Redirect loops happen when two layers keep sending the browser back and forth. The fix is to locate the layer producing each Location header.

Symptoms

  • Browser shows too many redirects.
  • curl -IL repeats the same URLs or alternates between hosts.
  • The loop appears only behind a CDN or reverse proxy.

Likely causes

  • HTTPS redirects are configured in both Nginx and CDN with conflicting assumptions.
  • www and non-www rules point at each other.
  • Application code redirects after Nginx already canonicalized the URL.

Fix steps

  1. Use curl -IL to list each redirect hop and Location header.
  2. Keep canonical host redirects in one layer when possible.
  3. Review server blocks before generic proxy rules and run nginx -t before reload.

Verify the fix

  • Run nginx -t.
  • Run curl -IL http://example.com/path and https://example.com/path.
  • Check CDN rules if the origin works but public traffic loops.

FAQ

Is a redirect loop always an Nginx bug?

No. It may come from CDN, load balancer, application middleware or mixed rules.

Should I use 301 while testing?

Use 302 for uncertain tests, then switch to 301 after behavior is confirmed.

Related tools and guides

Nginx Nginx Redirect Generator

Generate Nginx redirect snippets for moved pages, HTTPS upgrades, and canonical host cleanup.

 Nginx Nginx Config Validator Helper

Review pasted Nginx snippets for common mistakes and generate safe test, reload and curl verification commands.

 HTTP HTTP Headers Checker

Analyze pasted HTTP response headers for cache, redirects, security headers and content-type issues without making server-side requests.

 Nginx Nginx 301 Redirect Workflow With Safe Testing

Redirect changes are small but risky. A safe workflow generates a narrow rule, validates Nginx syntax, tests Location headers and keeps rollback simple.

Last updated: May 18, 2026