The HTTP 302
Found
redirect status response code indicates that the resource requested has been temporarily moved to the URL given by the {{HTTPHeader("Location")}} headers. Browser redirects to this page, but search engines updates their link to the resource (In SEO-speak, it is said that the link-juice is not sent to the new URL).
Even if the specification requires the method, and the body, not to be altered when the redirection is performed, not all user-agents did it, and you can still find buggy software out there. It is therefore recommended to the 301
code only as a return for {{HTTPMethod("GET")}} or {{HTTPMethod("HEAD")}} methods an to use {{HTTPStatus("307")}} Temporary Redirect
instead, as the method change is explicitly prohibited in that case.
In the cases where you want the method used to be changed to {{HTTPMethod("GET")}}, use {{HTTPStatus("303")}} See Also
instead. This is useful when you want to give an answer to a {{HTTPMethod("PUT")}} method that is not the uploaded resources, but a confirmation message (like "You successfully uploaded XYZ").
Status
302 Found
Specifications
Specification | Title |
---|---|
{{RFC("7231", "302 Found" , "6.4.3")}} | Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content |
Browser compatibility
The compatibility table in this page is generated from structured data. If you’d like to contribute to the data, please check out https://github.com/mdn/browser-compat-data/README.md and send us a pull request.
{{Compat}}
See also
- {{HTTPStatus("308")}}
Temporary Redirect
, the equivalent of this status code, but that never changes the method used. - {{HTTPStatus("303")}}
See Also
, a temporary redirect that changes the metod used to {{HTTPMethod("GET")}}. - {{HTTPStatus("301")}}
Found
, the temporary redirect