HTTP status · 3xx — redirection
302 Found
302 Found says the resource is temporarily available at another URL, and the original URL should remain the address clients use.
Key facts
| Class | 3xx — redirection |
|---|---|
| Standard | RFC 9110 §15.4.3 |
| Cacheable by default | No |
| Method handling | May be changed to GET (except HEAD) |
| Typical use | Temporary campaign, A/B route, login bounce |
What 302 means
The target resource is temporarily reachable at the URI in Location. Unlike 301, the move is not permanent: clients should keep using the original URI, and caches should not assume the redirect will persist. Browsers still usually follow it transparently, which can make a temporary route look permanent from the user's side.
When 302 is the wrong code
If a page has moved for good, use 301 or 308 — a 302 leaves search engines pointing at the old URL and wastes link signals. If the method must be preserved during a temporary redirect, use 307. A 302 on a POST may be turned into a GET, which can drop the body; that behaviour is historical but still allowed.
Frequently asked questions
Is 302 cached?
Not by default. A cache may store it only when explicit Cache-Control or Expires headers allow it.
302 or 307 for a temporary redirect?
Use 307 when the request method and body must survive the redirect, such as a POST. Use 302 for ordinary GET page redirects.