HTTP status code 302 — Found
Quick answer
Status code 302 (Found): Temporary redirect. Often used in login flows; not as strong for SEO as 301.
Often used in login flows; not as strong for SEO as 301.
Historically 302 allows method changes on redirect. For a permanent move use 301; for “reuse the same method” prefer 307/308.
Common causes
- Post-login redirect back to the originally requested page
- A/B testing or maintenance-mode routing
How to fix it
If you built this redirect and it is actually permanent, switch to 301/308 — search engines treat 302 as temporary and keep indexing the old URL.
Frequently asked questions
What is status code 302?
302 Found: Temporary redirect. Often used in login flows; not as strong for SEO as 301.
When should I expect HTTP 302?
Historically 302 allows method changes on redirect. For a permanent move use 301; for “reuse the same method” prefer 307/308.
What usually causes HTTP 302?
Post-login redirect back to the originally requested page; A/B testing or maintenance-mode routing.
How do I fix HTTP 302?
If you built this redirect and it is actually permanent, switch to 301/308 — search engines treat 302 as temporary and keep indexing the old URL.
Where can I see all status codes?
Open the HTTP status codes hub on TryDevSnip for the full reference list.
Does TryDevSnip log my API traffic?
No. These pages are static reference. TryDevSnip does not proxy or inspect your HTTP calls.