302 Found

A temporary redirect: use the Location URL this time, but keep requesting the original URL in the future. Browsers don't durably cache it, which makes 302 the safe testing ground before committing to a 301.

What usually causes it

  • Login flows (redirect to sign-in, then back)
  • A/B tests and geo-based routing
  • Maintenance splashes and temporary moves

How to debug and fix it

  1. If a redirect should be permanent (and cached, and pass SEO signal), upgrade it to 301/308 once verified.
  2. POST bodies vanish through 302s in many clients (downgraded to GET) — use 307 when the method and body must survive.
  3. Redirect loops (ERR_TOO_MANY_REDIRECTS) are usually conflicting rules — e.g. app forcing https while the proxy forwards http; check X-Forwarded-Proto handling.

Easily confused with

Debugging an API? Build and inspect requests, check response headers, or read the full status-code debugging guide.