Mirrors/httpstatuses
1
0
Fork 0
mirror of https://github.com/rmaake1/httpstatuses.git synced 2024-10-04 15:17:23 +02:00
Code Issues Packages Projects Releases Wiki Activity

Fixed 3xx code source reference numbering

Browse Source
This commit is contained in:
Samuel Ryan 2015-11-07 03:04:37 +00:00
parent 63a1095be6
commit 62dd681756
2 changed files with 12 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
contents/codes/300.md
View File

@ -13,7 +13,7 @@ information about the alternatives is being provided so that the user (or user
agent) can select a preferred representation by redirecting its request to one
or more of those identifiers. In other words, the server desires that the user
agent engage in reactive negotiation to select the most appropriate
representation(s) for its needs ([RFC7231 Section 3.4][1]).
representation(s) for its needs ([RFC7231 Section 3.4][2]).
If the server has a preferred choice, the server SHOULD generate a Location
header field containing a preferred choice's URI reference. The user agent MAY
@ -31,7 +31,7 @@ design or content negotiation, or in some commonly accepted hypertext format.
A 300 response is cacheable by default; i.e., unless otherwise indicated by the
method definition or explicit cache controls (see
[Section 4.2.2 of RFC7234][2]).
[Section 4.2.2 of RFC7234][3]).
Note: The original proposal for the 300 status code defined the URI header field
as providing a list of alternative representations, such that it would be usable
@ -39,12 +39,12 @@ for 200, 300, and 406 responses and be transferred in responses to the HEAD
method. However, lack of deployment and disagreement over syntax led to both URI
and Alternates (a subsequent proposal) being dropped from this specification. It
is possible to communicate the list using a set of Link header fields
[[RFC5988][3]], each with a relationship of "alternate", though deployment is a
[[RFC5988][4]], each with a relationship of "alternate", though deployment is a
chicken-and-egg problem.
Source: [RFC7231 Section 6.4.1][4]
Source: [RFC7231 Section 6.4.1][1]
[1]: <http://tools.ietf.org/html/rfc7231#section-3.4>
[2]: <http://tools.ietf.org/html/rfc7234#section-4.2.2>
[3]: <http://tools.ietf.org/html/rfc5988>
[4]: <http://tools.ietf.org/html/rfc7231#section-6.4.1>
[1]: <http://tools.ietf.org/html/rfc7231#section-6.4.1>
[2]: <http://tools.ietf.org/html/rfc7231#section-3.4>
[3]: <http://tools.ietf.org/html/rfc7234#section-4.2.2>
[4]: <http://tools.ietf.org/html/rfc5988>

8
contents/codes/301.md
View File

@ -23,9 +23,9 @@ POST to GET for the subsequent request. If this behavior is undesired, the
A 301 response is cacheable by default; i.e., unless otherwise indicated by the
method definition or explicit cache controls
(see [Section 4.2.2 of [RFC7234]][1]).
(see [Section 4.2.2 of [RFC7234]][2]).
Source: [RFC7231 Section 6.4.2][2]
Source: [RFC7231 Section 6.4.2][1]
[1]: <http://tools.ietf.org/html/rfc7234#section-4.2.2>
[2]: <http://tools.ietf.org/html/rfc7231#section-6.4.2>
[1]: <http://tools.ietf.org/html/rfc7231#section-6.4.2>
[2]: <http://tools.ietf.org/html/rfc7234#section-4.2.2>