2015-11-06 21:39:33 +01:00
|
|
|
---
|
|
|
|
|
set: 3
|
|
|
|
|
code: 302
|
|
|
|
|
title: Found
|
2015-11-07 03:57:14 +01:00
|
|
|
references:
|
|
|
|
|
"Rails HTTP Status Symbol": ":found"
|
2015-11-06 21:39:33 +01:00
|
|
|
---
|
|
|
|
|
|
2015-11-07 06:34:45 +01:00
|
|
|
The 302 Found status code indicates that the target resource resides temporarily
|
|
|
|
|
under a different URI. Since the redirection might be altered on
|
2015-11-07 03:57:14 +01:00
|
|
|
occasion, the client ought to continue to use the effective request URI for
|
|
|
|
|
future requests.
|
|
|
|
|
|
|
|
|
|
The server SHOULD generate a Location header field in the response containing a
|
|
|
|
|
URI reference for the different URI. The user agent MAY use the Location field
|
|
|
|
|
value for automatic redirection. The server's response payload usually contains
|
|
|
|
|
a short hypertext note with a hyperlink to the different URI(s).
|
|
|
|
|
|
|
|
|
|
Note: For historical reasons, a user agent MAY change the request method from
|
|
|
|
|
POST to GET for the subsequent request. If this behavior is undesired, the
|
|
|
|
|
[307 (Temporary Redirect)](/307) status code can be used instead.
|
|
|
|
|
|
|
|
|
|
Source: [RFC7231 Section 6.4.3][1]
|
|
|
|
|
|
|
|
|
|
[1]: <http://tools.ietf.org/html/rfc7231#section-6.4.3>
|
