HTTP 302 Found

Status code 302 · Class 3xx

HTTP

Found

Also searched as: HTTP 302, 302 redirect, 302 found

HTTP request chain from browser through CDN and proxy to the origin server
HTTP errors: find which hop in the request chain failed and read its logs.

What it means

302 is a temporary redirect: the resource is currently at another URL, but clients should keep using the original one. Login flows and A/B tests use it. It is not an error unless it loops or is used for a permanent move.

Applies to: All browsers, nginx, Apache, IIS

How to fix HTTP 302 Found

  1. If you are stuck in a login loop, clear cookies for the site and log in again
  2. Inspect redirects with 'curl -sIL https://example.com' or the DevTools Network tab with 'Preserve log' checked
  3. If you own the site: use 301 or 308 for permanent moves so search engines update their index
  4. If you own the site: use 303 after handling a form POST to send the browser to a result page with GET
  5. If you own the site: use 307 if the original method and body must be repeated at the new location

Why it happens

RFC 9110 defines 302 as a temporary relocation. Historically browsers change POST to GET when following it, which is why 303 and 307 were introduced to make intent explicit.

FAQ

Is a 302 redirect bad for SEO?

Not when the move really is temporary. For permanent moves, use 301 so signals transfer clearly to the new URL.

Related errors

HTTP 301 Moved PermanentlyHTTP 304 Not ModifiedHTTP 303 See OtherHTTP 409 ConflictHTTP 410 GoneHTTP 413 Content Too LargeHTTP 422 Unprocessable ContentHTTP 429 Too Many Requests

Source: IANA HTTP Status Code Registry · fixes written and reviewed by the editors (see our editorial policy)

Last updated: