redirect RFC 9110
HTTP 302 Found
Resource is temporarily at a different URL — do not update bookmarks or search engine indexes.
What it means
A temporary redirect. Historically 302 changed the HTTP method (POST to the original URL → GET to the new URL), which caused enough confusion that RFC 7231 introduced 303 (always GET) and 307 (preserve method) for clarity. Most modern APIs should return 303 or 307 explicitly. 302 remains common for auth flows (`302` back to /login after a session expires).
When servers send it
- •A/B test or feature flag routing users to a different URL
- •Session-expired redirect back to login
- •Load balancer sending you to a specific region
What the client does
Follows to the new URL. Does not update its cache or bookmarks. Some old clients change POST to GET.
When you see it
- •Intentional temporary redirect
Similar codes
301 Moved Permanently redirect
The resource has permanently moved to a new URL — clients and search engines should update their references.
307 Temporary Redirect redirect
Same as 302 but explicitly preserves the HTTP method — POST stays POST.
308 Permanent Redirect redirect
Same as 301 but explicitly preserves the HTTP method — POST stays POST.
304 Not Modified redirect
The cached copy the client already has is still valid — no body sent.
← All HTTP status codes · HTTP status cheat sheet · HTTP headers reference