302 Found

The HTTP 302 Found 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).

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, and you can still find buggy software out there. It is therefore recommended to set the 301 code only as a response for GET or HEAD methods and to use 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 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 resource, but a confirmation message (like "You successfully uploaded XYZ").


302 Found


Specification Title
RFC 7231, section 6.4.3: 302 Found Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content

Browser compatibility

Feature Chrome Edge Firefox Internet Explorer Opera Safari Servo
Basic Support(Yes)(Yes)(Yes)(Yes)(Yes)(Yes)(Yes)
Feature Android Chrome for Android Edge Mobile Firefox for Android IE Mobile Opera Mobile Safari Mobile
Basic Support(Yes)(Yes)(Yes)(Yes)(Yes)(Yes)(Yes)

See also

  • 307 Temporary Redirect, the equivalent of this status code, but that never changes the method used.
  • 303 See Also, a temporary redirect that changes the method used to GET.
  • 301 Found, the temporary redirect.

Document Tags and Contributors

 Contributors to this page: fscholz, teoli
 Last updated by: fscholz,