What 302 Found means

302 Found means the resource is temporarily available at another URL given in Location. The client should continue to use the original URL for future requests. It is not permanently cacheable by default, though caches may still store it briefly.

When a server should return it

  • Redirecting unauthenticated users to a login page.
  • Serving a maintenance page while the backend is upgraded.
  • Temporary campaign or experiment routing.
  • Short links where the destination may change.

Example response

http
HTTP/1.1 302 Found
Location: /login?next=/settings
Cache-Control: no-store

Why you might see it unexpectedly

  • A load balancer or auth proxy redirecting when a session cookie is missing.
  • Mixed http/https content causing an unexpected redirect loop.
  • A/B testing middleware that redirects users into variant URLs.

Related status codes

301 Moved Permanently for permanent moves. 307 Temporary Redirect preserves the method. 303 See Other explicitly tells the client to GET the new URL.