Developer
Encoders, converters & dev utilities
302 Found
HTTP 302 Found. The resource is temporarily at a different URL (Location header). It is temporary, so clients should keep using the original URL. Historically many browsers changed the method to GET on the redirect, which is why 307 exists. When to use it: Use for a temporary redirect where method-rewriting to GET is acceptable; prefer 307 when the method and body must be preserved. It is a redirection (3xx) status, so the client is expected to follow the Location header to another URL. (Reference: RFC 9110 §15.4.3.)
The resource is temporarily at a different URL (Location header). It is temporary, so clients should keep using the original URL. Historically many browsers changed the method to GET on the redirect, which is why 307 exists.
- When to use: Use for a temporary redirect where method-rewriting to GET is acceptable; prefer 307 when the method and body must be preserved.
- No fix needed — Found is not an error to resolve on the client side.
- Reference: RFC 9110 §15.4.3
- Category: 3xx Redirection
Frequently asked questions
What does HTTP 302 mean?
HTTP 302 Found: The resource is temporarily at a different URL (Location header). It is temporary, so clients should keep using the original URL. Historically many browsers changed the method to GET on the redirect, which is why 307 exists. It is a redirection (3xx) status, so the client is expected to follow the Location header to another URL. It is defined in RFC 9110 §15.4.3.
What is the difference between 302 and 307?
302 Found and 307 Temporary Redirect are both temporary, but they differ on method handling. Historically browsers often rewrote the request method to GET when following a 302 (so a POST became a GET). 307 was introduced to fix exactly that: it is a temporary redirect that must preserve the original method and body. Use 307 when you need a POST to stay a POST across the redirect.