307 Temporary Redirect

This response code indicates that the requested resource has been moved temporarily. The location of the new resource is indicated in the Location header.

As with other temporary redirects search engines will not update their links to reflect the new URL.

This temporary redirect differs from others in that it promises that the method and contents of the requested resource have not been changed.

This form of redirect is most often used when the admins need ensure certain methods and body contents are available through the redirect.

If this message is unexpected the user should verify the method of request and re-attempt. If the issue persists and users are unable to access the desired content, then they should contact support.

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 Other 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.