2015-11-06 22:55:41 +01:00
|
|
|
---
|
|
|
|
|
set: 3
|
|
|
|
|
code: 308
|
|
|
|
|
title: Permanent Redirect
|
|
|
|
|
---
|
|
|
|
|
|
2015-11-07 06:34:45 +01:00
|
|
|
The 308 Permanent Redirect status code indicates that the target resource has
|
2015-11-07 03:57:14 +01:00
|
|
|
been assigned a new permanent URI and any future references to this resource
|
2015-11-07 06:34:45 +01:00
|
|
|
ought to use one of the enclosed URIs.
|
|
|
|
|
|
|
|
|
|
Clients with link editing capabilities ought to automatically re-link references
|
|
|
|
|
to the effective request URI ([Section 5.5 of RFC7230][2]) to one or more of the
|
|
|
|
|
new references sent by the server, where possible.
|
2015-11-07 03:57:14 +01:00
|
|
|
|
|
|
|
|
The server SHOULD generate a Location header field
|
|
|
|
|
([[RFC7231], Section 7.1.2][3]) in the response containing a preferred URI
|
|
|
|
|
reference for the new permanent 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 new URI(s).
|
|
|
|
|
|
|
|
|
|
A 308 response is cacheable by default; i.e., unless otherwise indicated by the
|
|
|
|
|
method definition or explicit cache controls ([see RFC7234, Section 4.2.2][4]).
|
|
|
|
|
|
|
|
|
|
Note: This status code is similar to 301 (Moved Permanently)
|
|
|
|
|
([RFC7231, Section 6.4.2][5]), except that it does not allow changing the
|
|
|
|
|
request method from POST to GET.
|
|
|
|
|
|
|
|
|
|
Source: [RFC738 Section 3][1]
|
|
|
|
|
|
|
|
|
|
[1]: <http://tools.ietf.org/html/rfc7538#section-3>
|
|
|
|
|
[2]: <http://tools.ietf.org/html/rfc7230#section-5.5>
|
|
|
|
|
[3]: <http://tools.ietf.org/html/rfc7231#section-7.1.2>
|
|
|
|
|
[4]: <http://tools.ietf.org/html/rfc7234#section-4.2.2>
|
|
|
|
|
[5]: <http://tools.ietf.org/html/rfc7231#section-6.4.2>
|
