httpstatuses/contents/codes/308.md
Samuel Ryan d8a693bf27 Remove markdown line limit (#52)
* Removes line length limit from Status Code Markdown

This will make the data easier to use when we develop the API, it needs
to be consistent, arbitrary new lines (especially in text format) will
be a major issue, so some sort of workaround would have to be
implemented, easier to simply fix the source files.

* Removes line length limit from misc. Markdown files
2016-04-23 01:12:07 +01:00

32 lines
1.6 KiB
Markdown

---
set: 3
code: 308
title: Permanent Redirect
references:
"Symfony HTTP Status Constant": "Response::HTTP_PERMANENTLY_REDIRECT"
---
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.
Clients with link editing capabilities ought to automatically re-link references to the effective request URI<sup>[1](#ref-1)</sup> to one or more of the new references sent by the server, where possible.
The server SHOULD generate a Location header field<sup>[2](#ref-2)</sup> 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<sup>[3](#ref-3)</sup>.
Note: This status code is similar to [301 Moved Permanently](/301), except that it does not allow changing the request method from POST to GET.
---
* <span id="ref-1"><sup>1</sup> Effective Request URI
[RFC7230 Section 5.5][2]</span>
* <span id="ref-2"><sup>2</sup> Location [RFC7231 Section 7.1.2][3]</span>
* <span id="ref-3"><sup>3</sup> Calculating Heuristic Freshness
[RFC7234 Section 4.2.2][4]</span>
* 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>