The HTTP 307
Temporary Redirect
redirect status response code indicates that the resource requested has been temporarily moved to the URL given by the Location
headers.
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 GET
, use 303
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 307
and 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 behavior with 307
is predictable. For GET
requests, their behavior is identical.
Status
307 Temporary Redirect
Specifications
Specification | Title |
---|---|
RFC 7231, section 6.4.7: 307 Temporary Redirect | 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 and send us a pull request.
Feature | Chrome | Edge | Firefox | Internet Explorer | Opera | Safari |
---|---|---|---|---|---|---|
Basic Support | (Yes) | (Yes) | (Yes) | (Yes) | (Yes) | (Yes) |
Feature | Android | Chrome for Android | Edge mobile | Firefox for Android | IE mobile | Opera Android | iOS Safari |
---|---|---|---|---|---|---|---|
Basic Support | (Yes) | (Yes) | (Yes) | (Yes) | (Yes) | (Yes) | (Yes) |