HTTP 302 Found

The resource is temporarily at a different URL. Unlike a 301, the original URL stays authoritative and should still be used for future requests.

Defined in RFC 9110 §15.4.3 — 302 Found · MDN reference

Where you meet HTTP 302 in production

Post/Redirect/Get after a form submission, load-balancing a caller to a regional host, short-lived redirects to a signed download URL, and login flows that bounce a visitor through an identity provider and back.

Why you would test it

Confirm your client does not cache a 302 as if it were permanent, and that redirect loops are bounded rather than hanging.

What your client should do about a 302

Follow it, but keep the original URL — it is still the canonical address. Cap redirect following at a small number of hops so a redirect loop fails fast instead of hanging. If the method matters, remember that many clients turn the follow-up into a GET.

302 versus the codes it gets confused with

• 302 vs 301 Moved Permanently — 301 is permanent and will be cached. 302 is not.
• 302 vs 307 — 307 is the temporary redirect that preserves the method and body. Where a POST must stay a POST, 307 says so explicitly and 302 does not.

Endpoints that return 302

1 endpoint in this playground answers with 302. Every one is free, needs no signup, and can be called from the browser or with curl.

• GET https://funapi.dev/api/protocol/v1/hop — Redirects to /hop?hops=n-1 (Protocol Lab API) Open & run this endpoint

Questions about HTTP 302

Why is 302 sometimes described as "Found"?

That is its formal name. The behaviour people mean by it — "temporarily somewhere else" — is closer to what 307 defines precisely.

Is 302 bad for SEO?

Not bad, but it tells search engines to keep indexing the original URL. If the move is permanent, use 301.

Other redirection codes

• 301 Moved Permanently
• 304 Not Modified

All HTTP status codes · All 39 mock REST APIs · Getting started guide

Last updated 6 September 2026