The HyperText Transfer Protocol (HTTP)
302 Found redirect status response code indicates that the resource requested has been temporarily moved to the URL given by the
Location header. A browser redirects to this page but search engines don't update their links 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 conform here - you can still find this type of bugged software out there. It is therefore recommended to set the
302 code only as a response for
HEAD methods and to use
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
See Other instead. This is useful when you want to give a response to a
PUT method that is not the uploaded resource but a confirmation message such as: 'you successfully uploaded XYZ'.
|RFC 7231, section 6.4.3: 302 Found||Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content|
The information shown below has been pulled from MDN's Github (https://github.com/mdn/browser-compat-data).
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 and send us a pull request.
|Feature||Android webview||Chrome for Android||Edge mobile||Firefox for Android||IE mobile||Opera Android||iOS Safari|