308 Permanent Redirect

Takeaways

Permanent Redirect

1. The target resource has been assigned a new permanent URI and any future references to this resource ought to use one of the enclosed URIs.
2. Clients with link editing capabilities ought to automatically re-link references to the effective request URI to one or more of the new references sent by the server, where possible.
3. The server should generate a Location header field in the response containing a preferred URI reference for the new permanent URI.
4. The user agent may use the Location field value for automatic redirection.
5. 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.

Note

This status code is similar to 301 Moved Permanently, except that it does not allow changing the request method from POST to GET.

Resume Incomplete

Some applications may use 308 Resume Incomplete as a non-standard response.

1. This status code indicates to the client that the server does not possess the complete byte range for the resume request to proceed but is still willing to continue the operation.
2. It may include a Range header so that the client may minimize the amount of data that needs to be retransmitted by the ensuing resume requests.
3. In the absence of any such Range header, the client should assume that the server has no stored bytes.
4. It may include a Location header indicating the URI to which future resumable requests should be sent for this operation.

Information

A browser redirects to this page and search engines update their links to the resource (in 'SEO-speak', it is said that the 'link-juice' is sent to the new URL).