Temporary Redirect redirect status response code indicates that the resource requested has been temporarily moved to the URL given by the
Location headers. 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).
The method and the body of the original request are reused to perform the redirected request. In the cases where you want the method used to be changed to
See Also instead. This is useful when you want to give an answer to a
PUT method that is not the uploaded resources, but a confirmation message (like "You successfully uploaded XYZ").
The only difference between
302 is that
307 guarantees that the method and the body will not be changed when the redirected request is made. With
302, some old clients were incorrectly changing the method to
GET: the behavior with non-
GET methods and
302 is then unpredictable on the Web, whereas the
307 one is. For
GET requests, their behavior is identical.
307 Temporary Redirect
|RFC 7231, section 6.4.7: 307 Temporary Redirect||Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content|
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||Chrome for Android||Edge Mobile||Firefox for Android||IE Mobile||Opera Mobile||Safari Mobile|