Ignore:
Timestamp:
Jul 5, 2012, 10:06:19 AM (7 years ago)
Author:
julian.reschke@…
Message:

Work-in-progress: hyperlink status code range definitions

Location:
draft-ietf-httpbis/latest
Files:
8 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.html

    r1725 r1727  
    12821282      </p>
    12831283      <h3 id="rfc.section.3.2.3"><a href="#rfc.section.3.2.3">3.2.3</a>&nbsp;<a id="field.length" href="#field.length">Field Length</a></h3>
    1284       <p id="rfc.section.3.2.3.p.1">HTTP does not place a pre-defined limit on the length of header fields, either in isolation or as a set. A server <em class="bcp14">MUST</em> be prepared to receive request header fields of unbounded length and respond with a 4xx status code if the received header
    1285          field(s) would be longer than the server wishes to handle.
     1284      <p id="rfc.section.3.2.3.p.1">HTTP does not place a pre-defined limit on the length of header fields, either in isolation or as a set. A server <em class="bcp14">MUST</em> be prepared to receive request header fields of unbounded length and respond with a <a href="p2-semantics.html#status.4xx" class="smpl">4xx
     1285            (Client Error)</a> status code if the received header field(s) would be longer than the server wishes to handle.
    12861286      </p>
    12871287      <p id="rfc.section.3.2.3.p.2">A client that receives response headers that are longer than it wishes to handle can only treat it as a server error.</p>
     
    13761376      <p id="rfc.section.3.3.p.5">The presence of a message body in a response depends on both the request method to which it is responding and the response
    13771377         status code (<a href="#status-code">Paragraph&nbsp;3</a>). Responses to the HEAD request method never include a message body because the associated response header fields (e.g.,
    1378          Transfer-Encoding, Content-Length, etc.) only indicate what their values would have been if the request method had been GET.
    1379          Successful (2xx) responses to CONNECT switch to tunnel mode instead of having a message body. All 1xx (Informational), <a href="p2-semantics.html#status.204" class="smpl">204 (No Content)</a>, and <a href="p4-conditional.html#status.304" class="smpl">304
     1378         Transfer-Encoding, Content-Length, etc.) only indicate what their values would have been if the request method had been GET. <a href="p2-semantics.html#status.2xx" class="smpl">2xx (Successful)</a> responses to CONNECT switch to tunnel mode instead of having a message body. All <a href="p2-semantics.html#status.1xx" class="smpl">1xx (Informational)</a>, <a href="p2-semantics.html#status.204" class="smpl">204 (No Content)</a>, and <a href="p4-conditional.html#status.304" class="smpl">304
    13801379            (Not Modified)</a> responses <em class="bcp14">MUST NOT</em> include a message body. All other responses do include a message body, although the body <em class="bcp14">MAY</em> be of zero length. (See <a href="p2-semantics.html#status.codes" title="Status Codes">Section 4</a> of <a href="#Part2" id="rfc.xref.Part2.9"><cite title="HTTP/1.1, part 2: Message Semantics, Payload and Content Negotiation">[Part2]</cite></a> and <a href="p4-conditional.html#status.304" title="304 Not Modified">Section 4.1</a> of <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.)
    13811380      </p>
     
    14531452         </li>
    14541453         <li>
    1455             <p>Any successful (2xx) response to a CONNECT request implies that the connection will become a tunnel immediately after the
    1456                empty line that concludes the header fields. A client <em class="bcp14">MUST</em> ignore any Content-Length or Transfer-Encoding header fields received in such a message.
     1454            <p>Any <a href="p2-semantics.html#status.2xx" class="smpl">2xx (Successful)</a> response to a CONNECT request implies that the connection will become a tunnel immediately after the empty line that concludes
     1455               the header fields. A client <em class="bcp14">MUST</em> ignore any Content-Length or Transfer-Encoding header fields received in such a message.
    14571456            </p>
    14581457         </li>
     
    19771976         see <a href="p2-semantics.html#status.1xx" title="Informational 1xx">Section 4.3</a> of <a href="#Part2" id="rfc.xref.Part2.16"><cite title="HTTP/1.1, part 2: Message Semantics, Payload and Content Negotiation">[Part2]</cite></a>) precede a final response to the same request.
    19781977      </p>
    1979       <p id="rfc.section.5.7.p.2">A client that uses persistent connections and sends more than one request per connection <em class="bcp14">MUST</em> maintain a list of outstanding requests in the order sent on that connection and <em class="bcp14">MUST</em> associate each received response message to the highest ordered request that has not yet received a final (non-1xx) response.
     1978      <p id="rfc.section.5.7.p.2">A client that uses persistent connections and sends more than one request per connection <em class="bcp14">MUST</em> maintain a list of outstanding requests in the order sent on that connection and <em class="bcp14">MUST</em> associate each received response message to the highest ordered request that has not yet received a final (non-<a href="p2-semantics.html#status.1xx" class="smpl">1xx</a>) response.
    19801979      </p>
    19811980      <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="connection.management" href="#connection.management">Connection Management</a></h1>
     
    20212020      <p id="rfc.section.6.1.p.12">An HTTP/1.1 client that does not support persistent connections <em class="bcp14">MUST</em> include the "close" connection option in every request message.
    20222021      </p>
    2023       <p id="rfc.section.6.1.p.13">An HTTP/1.1 server that does not support persistent connections <em class="bcp14">MUST</em> include the "close" connection option in every response message that does not have a 1xx (Informational) status code.
     2022      <p id="rfc.section.6.1.p.13">An HTTP/1.1 server that does not support persistent connections <em class="bcp14">MUST</em> include the "close" connection option in every response message that does not have a <a href="p2-semantics.html#status.1xx" class="smpl">1xx (Informational)</a> status code.
    20242023      </p>
    20252024      <div id="rfc.iref.v.1"></div>
     
    22142213         </li>
    22152214         <li>A proxy <em class="bcp14">MUST NOT</em> forward a <a href="p2-semantics.html#status.100" class="smpl">100 (Continue)</a> response if the request message was received from an HTTP/1.0 (or earlier) client and did not include an Expect header field
    2216             with the "100-continue" expectation. This requirement overrides the general rule for forwarding of 1xx responses (see <a href="p2-semantics.html#status.1xx" title="Informational 1xx">Section 4.3</a> of <a href="#Part2" id="rfc.xref.Part2.22"><cite title="HTTP/1.1, part 2: Message Semantics, Payload and Content Negotiation">[Part2]</cite></a>).
     2215            with the "100-continue" expectation. This requirement overrides the general rule for forwarding of <a href="p2-semantics.html#status.1xx" class="smpl">1xx</a> responses (see <a href="p2-semantics.html#status.1xx" title="Informational 1xx">Section 4.3</a> of <a href="#Part2" id="rfc.xref.Part2.22"><cite title="HTTP/1.1, part 2: Message Semantics, Payload and Content Negotiation">[Part2]</cite></a>).
    22172216         </li>
    22182217      </ul>
     
    22512250      </p>
    22522251      <p id="rfc.section.6.5.p.8">The Upgrade header field cannot be used to indicate a switch to a protocol on a different connection. For that purpose, it
    2253          is more appropriate to use a 3xx redirection response (<a href="p2-semantics.html#status.3xx" title="Redirection 3xx">Section 4.5</a> of <a href="#Part2" id="rfc.xref.Part2.23"><cite title="HTTP/1.1, part 2: Message Semantics, Payload and Content Negotiation">[Part2]</cite></a>).
     2252         is more appropriate to use a <a href="p2-semantics.html#status.3xx" class="smpl">3xx (Redirection)</a> response (<a href="p2-semantics.html#status.3xx" title="Redirection 3xx">Section 4.5</a> of <a href="#Part2" id="rfc.xref.Part2.23"><cite title="HTTP/1.1, part 2: Message Semantics, Payload and Content Negotiation">[Part2]</cite></a>).
    22542253      </p>
    22552254      <p id="rfc.section.6.5.p.9">Servers <em class="bcp14">MUST</em> include the "Upgrade" header field in <a href="p2-semantics.html#status.101" class="smpl">101 (Switching
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r1726 r1727  
    12871287   HTTP does not place a pre-defined limit on the length of header fields,
    12881288   either in isolation or as a set. A server &MUST; be prepared to receive
    1289    request header fields of unbounded length and respond with a 4xx status
    1290    code if the received header field(s) would be longer than the server wishes
    1291    to handle.
     1289   request header fields of unbounded length and respond with a <x:ref>4xx
     1290   (Client Error)</x:ref> status code if the received header field(s) would be
     1291   longer than the server wishes to handle.
    12921292</t>
    12931293<t>
     
    14821482   Content-Length, etc.) only indicate what their values would have been
    14831483   if the request method had been GET.
    1484    Successful (2xx) responses to CONNECT switch to tunnel mode instead of
     1484   <x:ref>2xx (Successful)</x:ref> responses to CONNECT switch to tunnel mode instead of
    14851485   having a message body.
    1486    All 1xx (Informational), <x:ref>204 (No Content)</x:ref>, and <x:ref>304
     1486   All <x:ref>1xx (Informational)</x:ref>, <x:ref>204 (No Content)</x:ref>, and <x:ref>304
    14871487   (Not Modified)</x:ref> responses &MUST-NOT; include a message body.
    14881488   All other responses do include a message body, although the body
     
    16491649    </t></x:lt>
    16501650    <x:lt><t>
    1651      Any successful (2xx) response to a CONNECT request implies that the
     1651     Any <x:ref>2xx (Successful)</x:ref> response to a CONNECT request implies that the
    16521652     connection will become a tunnel immediately after the empty line that
    16531653     concludes the header fields.  A client &MUST; ignore any Content-Length
     
    26692669   order sent on that connection and &MUST; associate each received response
    26702670   message to the highest ordered request that has not yet received a final
    2671    (non-1xx) response.
     2671   (non-<x:ref>1xx</x:ref>) response.
    26722672</t>
    26732673</section>
     
    27612761   An HTTP/1.1 server that does not support persistent connections &MUST;
    27622762   include the "close" connection option in every response message that
    2763    does not have a 1xx (Informational) status code.
     2763   does not have a <x:ref>1xx (Informational)</x:ref> status code.
    27642764</t>
    27652765</section>
     
    31943194        client and did not include an Expect header field with
    31953195        the "100-continue" expectation. This requirement overrides the
    3196         general rule for forwarding of 1xx responses (see &status-1xx;).
     3196        general rule for forwarding of <x:ref>1xx</x:ref> responses (see &status-1xx;).
    31973197    </t>
    31983198  </list>
     
    32723272   The Upgrade header field cannot be used to indicate a switch to a
    32733273   protocol on a different connection. For that purpose, it is more
    3274    appropriate to use a 3xx redirection response (&status-3xx;).
     3274   appropriate to use a <x:ref>3xx (Redirection)</x:ref> response (&status-3xx;).
    32753275</t>
    32763276<t>
     
    41094109  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p2-semantics-&ID-VERSION;"/>
    41104110  <x:source href="p2-semantics.xml" basename="p2-semantics">
     4111    <x:defines>1xx (Informational)</x:defines>
     4112    <x:defines>1xx</x:defines>
    41114113    <x:defines>100 (Continue)</x:defines>
    41124114    <x:defines>101 (Switching Protocols)</x:defines>
     4115    <x:defines>2xx (Successful)</x:defines>
     4116    <x:defines>2xx</x:defines>
    41134117    <x:defines>200 (OK)</x:defines>
    41144118    <x:defines>204 (No Content)</x:defines>
     4119    <x:defines>3xx (Redirection)</x:defines>
     4120    <x:defines>3xx</x:defines>
    41154121    <x:defines>301 (Moved Permanently)</x:defines>
     4122    <x:defines>4xx (Client Error)</x:defines>
     4123    <x:defines>4xx</x:defines>
    41164124    <x:defines>400 (Bad Request)</x:defines>
    41174125    <x:defines>405 (Method Not Allowed)</x:defines>
  • draft-ietf-httpbis/latest/p2-semantics.html

    r1726 r1727  
    11311131Host: server.example.com:80
    11321132
    1133 </pre><p id="rfc.section.2.3.8.p.4">Any successful (2xx) response to a CONNECT request indicates that the proxy has established a connection to the requested
    1134          host and port, and has switched to tunneling the current connection to that server connection. The tunneled data from the
    1135          server begins immediately after the blank line that concludes the successful response's header block. A server <em class="bcp14">SHOULD NOT</em> send any Transfer-Encoding or Content-Length header fields in a successful response. A client <em class="bcp14">MUST</em> ignore any Content-Length or Transfer-Encoding header fields received in a successful response.
     1133</pre><p id="rfc.section.2.3.8.p.4">Any <a href="#status.2xx" class="smpl">2xx (Successful)</a> response to a CONNECT request indicates that the proxy has established a connection to the requested host and port, and has
     1134         switched to tunneling the current connection to that server connection. The tunneled data from the server begins immediately
     1135         after the blank line that concludes the successful response's header block. A server <em class="bcp14">SHOULD NOT</em> send any Transfer-Encoding or Content-Length header fields in a successful response. A client <em class="bcp14">MUST</em> ignore any Content-Length or Transfer-Encoding header fields received in a successful response.
    11361136      </p>
    11371137      <p id="rfc.section.2.3.8.p.5">Any response other than a successful response indicates that the tunnel has not yet been formed and that the connection remains
     
    11501150      </p>
    11511151      <p id="rfc.section.2.3.8.p.10">It might be the case that the proxy itself can only reach the requested origin server through another proxy. In this case,
    1152          the first proxy <em class="bcp14">SHOULD</em> make a CONNECT request of that next proxy, requesting a tunnel to the authority. A proxy <em class="bcp14">MUST NOT</em> respond with any 2xx status code unless it has either a direct or tunnel connection established to the authority.
     1152         the first proxy <em class="bcp14">SHOULD</em> make a CONNECT request of that next proxy, requesting a tunnel to the authority. A proxy <em class="bcp14">MUST NOT</em> respond with any <a href="#status.2xx" class="smpl">2xx</a> status code unless it has either a direct or tunnel connection established to the authority.
    11531153      </p>
    11541154      <p id="rfc.section.2.3.8.p.11">If at any point either one of the peers gets disconnected, any outstanding data that came from that peer will be passed to
     
    11561156         peer undelivered, that data will be discarded.
    11571157      </p>
    1158       <p id="rfc.section.2.3.8.p.12">An origin server which receives a CONNECT request for itself <em class="bcp14">MAY</em> respond with a 2xx status code to indicate that a connection is established. However, most origin servers do not implement
    1159          CONNECT.
     1158      <p id="rfc.section.2.3.8.p.12">An origin server which receives a CONNECT request for itself <em class="bcp14">MAY</em> respond with a <a href="#status.2xx" class="smpl">2xx</a> status code to indicate that a connection is established. However, most origin servers do not implement CONNECT.
    11601159      </p>
    11611160      <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="header.fields" href="#header.fields">Header Fields</a></h1>
     
    13911390      </p>
    13921391      <ul>
    1393          <li>1xx: Informational - Request received, continuing process</li>
    1394          <li>2xx: Success - The action was successfully received, understood, and accepted</li>
    1395          <li>3xx: Redirection - Further action needs to be taken in order to complete the request</li>
    1396          <li>4xx: Client Error - The request contains bad syntax or cannot be fulfilled</li>
    1397          <li>5xx: Server Error - The server failed to fulfill an apparently valid request</li>
     1392         <li> <a href="#status.1xx" class="smpl">1xx (Informational)</a>: Request received, continuing process
     1393         </li>
     1394         <li> <a href="#status.2xx" class="smpl">2xx (Successful)</a>: The action was successfully received, understood, and accepted
     1395         </li>
     1396         <li> <a href="#status.3xx" class="smpl">3xx (Redirection)</a>: Further action needs to be taken in order to complete the request
     1397         </li>
     1398         <li> <a href="#status.4xx" class="smpl">4xx (Client Error)</a>: The request contains bad syntax or cannot be fulfilled
     1399         </li>
     1400         <li> <a href="#status.5xx" class="smpl">5xx (Server Error)</a>: The server failed to fulfill an apparently valid request
     1401         </li>
    13981402      </ul>
    13991403      <p id="rfc.section.4.p.4">For most status codes the response can carry a payload, in which case a Content-Type header field indicates the payload's
     
    16471651      </p>
    16481652      <h2 id="rfc.section.4.3"><a href="#rfc.section.4.3">4.3</a>&nbsp;<a id="status.1xx" href="#status.1xx">Informational 1xx</a></h2>
     1653      <div id="rfc.iref.21"></div>
     1654      <div id="rfc.iref.s.3"></div>
    16491655      <p id="rfc.section.4.3.p.1">This class of status code indicates a provisional response, consisting only of the status-line and optional header fields,
    16501656         and is terminated by an empty line. There are no required header fields for this class of status code. Since HTTP/1.0 did
     
    16581664         a request, then it need not forward the corresponding <a href="#status.100" class="smpl">100 (Continue)</a> response(s).)
    16591665      </p>
    1660       <div id="rfc.iref.21"></div>
    1661       <div id="rfc.iref.s.3"></div>
     1666      <div id="rfc.iref.22"></div>
     1667      <div id="rfc.iref.s.4"></div>
    16621668      <h3 id="rfc.section.4.3.1"><a href="#rfc.section.4.3.1">4.3.1</a>&nbsp;<a id="status.100" href="#status.100">100 Continue</a></h3>
    16631669      <p id="rfc.section.4.3.1.p.1">The client <em class="bcp14">SHOULD</em> continue with its request. This interim response is used to inform the client that the initial part of the request has been
     
    16651671         server <em class="bcp14">MUST</em> send a final response after the request has been completed. See <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 6.4.3</a> of <a href="#Part1" id="rfc.xref.Part1.32"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for detailed discussion of the use and handling of this status code.
    16661672      </p>
    1667       <div id="rfc.iref.22"></div>
    1668       <div id="rfc.iref.s.4"></div>
     1673      <div id="rfc.iref.23"></div>
     1674      <div id="rfc.iref.s.5"></div>
    16691675      <h3 id="rfc.section.4.3.2"><a href="#rfc.section.4.3.2">4.3.2</a>&nbsp;<a id="status.101" href="#status.101">101 Switching Protocols</a></h3>
    16701676      <p id="rfc.section.4.3.2.p.1">The server understands and is willing to comply with the client's request, via the Upgrade message header field (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 6.5</a> of <a href="#Part1" id="rfc.xref.Part1.33"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>), for a change in the application protocol being used on this connection. The server will switch protocols to those defined
     
    16761682      </p>
    16771683      <h2 id="rfc.section.4.4"><a href="#rfc.section.4.4">4.4</a>&nbsp;<a id="status.2xx" href="#status.2xx">Successful 2xx</a></h2>
     1684      <div id="rfc.iref.24"></div>
     1685      <div id="rfc.iref.s.6"></div>
    16781686      <p id="rfc.section.4.4.p.1">This class of status code indicates that the client's request was successfully received, understood, and accepted.</p>
    1679       <div id="rfc.iref.23"></div>
    1680       <div id="rfc.iref.s.5"></div>
     1687      <div id="rfc.iref.25"></div>
     1688      <div id="rfc.iref.s.7"></div>
    16811689      <h3 id="rfc.section.4.4.1"><a href="#rfc.section.4.4.1">4.4.1</a>&nbsp;<a id="status.200" href="#status.200">200 OK</a></h3>
    16821690      <p id="rfc.section.4.4.1.p.1">The request has succeeded. The payload returned with the response is dependent on the method used in the request, for example: </p>
     
    16931701      <p id="rfc.section.4.4.1.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.11"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 200 responses.
    16941702      </p>
    1695       <div id="rfc.iref.24"></div>
    1696       <div id="rfc.iref.s.6"></div>
     1703      <div id="rfc.iref.26"></div>
     1704      <div id="rfc.iref.s.8"></div>
    16971705      <h3 id="rfc.section.4.4.2"><a href="#rfc.section.4.4.2">4.4.2</a>&nbsp;<a id="status.201" href="#status.201">201 Created</a></h3>
    16981706      <p id="rfc.section.4.4.2.p.1">The request has been fulfilled and has resulted in one or more new resources being created.</p>
     
    17061714         identified by the Location header field or, in case the Location header field was omitted, by the Effective Request URI (see <a href="p4-conditional.html#header.etag" title="ETag">Section 2.3</a> of <a href="#Part4" id="rfc.xref.Part4.9"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>).
    17071715      </p>
    1708       <div id="rfc.iref.25"></div>
    1709       <div id="rfc.iref.s.7"></div>
     1716      <div id="rfc.iref.27"></div>
     1717      <div id="rfc.iref.s.9"></div>
    17101718      <h3 id="rfc.section.4.4.3"><a href="#rfc.section.4.4.3">4.4.3</a>&nbsp;<a id="status.202" href="#status.202">202 Accepted</a></h3>
    17111719      <p id="rfc.section.4.4.3.p.1">The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually
     
    17181726         user can expect the request to be fulfilled.
    17191727      </p>
    1720       <div id="rfc.iref.26"></div>
    1721       <div id="rfc.iref.s.8"></div>
     1728      <div id="rfc.iref.28"></div>
     1729      <div id="rfc.iref.s.10"></div>
    17221730      <h3 id="rfc.section.4.4.4"><a href="#rfc.section.4.4.4">4.4.4</a>&nbsp;<a id="status.203" href="#status.203">203 Non-Authoritative Information</a></h3>
    17231731      <p id="rfc.section.4.4.4.p.1">The representation in the response has been transformed or otherwise modified by a transforming proxy (<a href="p1-messaging.html#intermediaries" title="Intermediaries">Section 2.3</a> of <a href="#Part1" id="rfc.xref.Part1.34"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). Note that the behavior of transforming intermediaries is controlled by the no-transform Cache-Control directive (<a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 3.2</a> of <a href="#Part6" id="rfc.xref.Part6.12"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
     
    17281736      <p id="rfc.section.4.4.4.p.3">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.14"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 203 responses.
    17291737      </p>
    1730       <div id="rfc.iref.27"></div>
    1731       <div id="rfc.iref.s.9"></div>
     1738      <div id="rfc.iref.29"></div>
     1739      <div id="rfc.iref.s.11"></div>
    17321740      <h3 id="rfc.section.4.4.5"><a href="#rfc.section.4.4.5">4.4.5</a>&nbsp;<a id="status.204" href="#status.204">204 No Content</a></h3>
    17331741      <p id="rfc.section.4.4.5.p.1">The 204 (No Content) status code indicates that the server has successfully fulfilled the request and that there is no additional
     
    17491757      <p id="rfc.section.4.4.5.p.5">The 204 response <em class="bcp14">MUST NOT</em> include a message body, and thus is always terminated by the first empty line after the header fields.
    17501758      </p>
    1751       <div id="rfc.iref.28"></div>
    1752       <div id="rfc.iref.s.10"></div>
     1759      <div id="rfc.iref.30"></div>
     1760      <div id="rfc.iref.s.12"></div>
    17531761      <h3 id="rfc.section.4.4.6"><a href="#rfc.section.4.4.6">4.4.6</a>&nbsp;<a id="status.205" href="#status.205">205 Reset Content</a></h3>
    17541762      <p id="rfc.section.4.4.6.p.1">The server has fulfilled the request and the user agent <em class="bcp14">SHOULD</em> reset the document view which caused the request to be sent. This response is primarily intended to allow input for actions
     
    17591767      </p>
    17601768      <h2 id="rfc.section.4.5"><a href="#rfc.section.4.5">4.5</a>&nbsp;<a id="status.3xx" href="#status.3xx">Redirection 3xx</a></h2>
     1769      <div id="rfc.iref.31"></div>
     1770      <div id="rfc.iref.s.13"></div>
    17611771      <p id="rfc.section.4.5.p.1">This class of status code indicates that further action needs to be taken by the user agent in order to fulfill the request.
    17621772         If the required action involves a subsequent HTTP request, it <em class="bcp14">MAY</em> be carried out by the user agent without interaction with the user if and only if the method used in the second request is
     
    18041814         </p>
    18051815      </div>
    1806       <div id="rfc.iref.29"></div>
    1807       <div id="rfc.iref.s.11"></div>
     1816      <div id="rfc.iref.32"></div>
     1817      <div id="rfc.iref.s.14"></div>
    18081818      <h3 id="rfc.section.4.5.1"><a href="#rfc.section.4.5.1">4.5.1</a>&nbsp;<a id="status.300" href="#status.300">300 Multiple Choices</a></h3>
    18091819      <p id="rfc.section.4.5.1.p.1">The target resource has more than one representation, each with its own specific location, and agent-driven negotiation information
     
    18191829      <p id="rfc.section.4.5.1.p.4">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.15"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 300 responses.
    18201830      </p>
    1821       <div id="rfc.iref.30"></div>
    1822       <div id="rfc.iref.s.12"></div>
     1831      <div id="rfc.iref.33"></div>
     1832      <div id="rfc.iref.s.15"></div>
    18231833      <h3 id="rfc.section.4.5.2"><a href="#rfc.section.4.5.2">4.5.2</a>&nbsp;<a id="status.301" href="#status.301">301 Moved Permanently</a></h3>
    18241834      <p id="rfc.section.4.5.2.p.1">The target resource has been assigned a new permanent URI and any future references to this resource <em class="bcp14">SHOULD</em> use one of the returned URIs. Clients with link editing capabilities ought to automatically re-link references to the effective
     
    18341844         </p>
    18351845      </div>
    1836       <div id="rfc.iref.31"></div>
    1837       <div id="rfc.iref.s.13"></div>
     1846      <div id="rfc.iref.34"></div>
     1847      <div id="rfc.iref.s.16"></div>
    18381848      <h3 id="rfc.section.4.5.3"><a href="#rfc.section.4.5.3">4.5.3</a>&nbsp;<a id="status.302" href="#status.302">302 Found</a></h3>
    18391849      <p id="rfc.section.4.5.3.p.1">The target resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client <em class="bcp14">SHOULD</em> continue to use the effective request URI for future requests.
     
    18461856         </p>
    18471857      </div>
    1848       <div id="rfc.iref.32"></div>
    1849       <div id="rfc.iref.s.14"></div>
     1858      <div id="rfc.iref.35"></div>
     1859      <div id="rfc.iref.s.17"></div>
    18501860      <h3 id="rfc.section.4.5.4"><a href="#rfc.section.4.5.4">4.5.4</a>&nbsp;<a id="status.303" href="#status.303">303 See Other</a></h3>
    18511861      <p id="rfc.section.4.5.4.p.1">The 303 status code indicates that the server is redirecting the user agent to a different resource, as indicated by a URI
     
    18671877      <p id="rfc.section.4.5.4.p.4">Except for responses to a HEAD request, the representation of a 303 response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the Location URI.
    18681878      </p>
    1869       <div id="rfc.iref.33"></div>
    1870       <div id="rfc.iref.s.15"></div>
     1879      <div id="rfc.iref.36"></div>
     1880      <div id="rfc.iref.s.18"></div>
    18711881      <h3 id="rfc.section.4.5.5"><a href="#rfc.section.4.5.5">4.5.5</a>&nbsp;<a id="status.305" href="#status.305">305 Use Proxy</a></h3>
    18721882      <p id="rfc.section.4.5.5.p.1">The 305 status code was defined in a previous version of this specification (see <a href="#changes.from.rfc.2616" title="Changes from RFC 2616">Appendix&nbsp;C</a>), and is now deprecated.
    18731883      </p>
    1874       <div id="rfc.iref.34"></div>
    1875       <div id="rfc.iref.s.16"></div>
     1884      <div id="rfc.iref.37"></div>
     1885      <div id="rfc.iref.s.19"></div>
    18761886      <h3 id="rfc.section.4.5.6"><a href="#rfc.section.4.5.6">4.5.6</a>&nbsp;<a id="status.306" href="#status.306">306 (Unused)</a></h3>
    18771887      <p id="rfc.section.4.5.6.p.1">The 306 status code was used in a previous version of the specification, is no longer used, and the code is reserved.</p>
    1878       <div id="rfc.iref.35"></div>
    1879       <div id="rfc.iref.s.17"></div>
     1888      <div id="rfc.iref.38"></div>
     1889      <div id="rfc.iref.s.20"></div>
    18801890      <h3 id="rfc.section.4.5.7"><a href="#rfc.section.4.5.7">4.5.7</a>&nbsp;<a id="status.307" href="#status.307">307 Temporary Redirect</a></h3>
    18811891      <p id="rfc.section.4.5.7.p.1">The target resource resides temporarily under a different URI. Since the redirection can change over time, the client <em class="bcp14">SHOULD</em> continue to use the effective request URI for future requests.
     
    18911901      </div>
    18921902      <h2 id="rfc.section.4.6"><a href="#rfc.section.4.6">4.6</a>&nbsp;<a id="status.4xx" href="#status.4xx">Client Error 4xx</a></h2>
     1903      <div id="rfc.iref.39"></div>
     1904      <div id="rfc.iref.s.21"></div>
    18931905      <p id="rfc.section.4.6.p.1">The 4xx class of status code is intended for cases in which the client seems to have erred. Except when responding to a HEAD
    18941906         request, the server <em class="bcp14">SHOULD</em> include a representation containing an explanation of the error situation, and whether it is a temporary or permanent condition.
    18951907         These status codes are applicable to any request method. User agents <em class="bcp14">SHOULD</em> display any included representation to the user.
    18961908      </p>
    1897       <div id="rfc.iref.36"></div>
    1898       <div id="rfc.iref.s.18"></div>
     1909      <div id="rfc.iref.40"></div>
     1910      <div id="rfc.iref.s.22"></div>
    18991911      <h3 id="rfc.section.4.6.1"><a href="#rfc.section.4.6.1">4.6.1</a>&nbsp;<a id="status.400" href="#status.400">400 Bad Request</a></h3>
    19001912      <p id="rfc.section.4.6.1.p.1">The server cannot or will not process the request, due to a client error (e.g., malformed syntax).</p>
    1901       <div id="rfc.iref.37"></div>
    1902       <div id="rfc.iref.s.19"></div>
     1913      <div id="rfc.iref.41"></div>
     1914      <div id="rfc.iref.s.23"></div>
    19031915      <h3 id="rfc.section.4.6.2"><a href="#rfc.section.4.6.2">4.6.2</a>&nbsp;<a id="status.402" href="#status.402">402 Payment Required</a></h3>
    19041916      <p id="rfc.section.4.6.2.p.1">This code is reserved for future use.</p>
    1905       <div id="rfc.iref.38"></div>
    1906       <div id="rfc.iref.s.20"></div>
     1917      <div id="rfc.iref.42"></div>
     1918      <div id="rfc.iref.s.24"></div>
    19071919      <h3 id="rfc.section.4.6.3"><a href="#rfc.section.4.6.3">4.6.3</a>&nbsp;<a id="status.403" href="#status.403">403 Forbidden</a></h3>
    19081920      <p id="rfc.section.4.6.3.p.1">The server understood the request, but refuses to authorize it. Providing different user authentication credentials might
     
    19131925            (Not Found)</a>  <em class="bcp14">MAY</em> be used instead.
    19141926      </p>
    1915       <div id="rfc.iref.39"></div>
    1916       <div id="rfc.iref.s.21"></div>
     1927      <div id="rfc.iref.43"></div>
     1928      <div id="rfc.iref.s.25"></div>
    19171929      <h3 id="rfc.section.4.6.4"><a href="#rfc.section.4.6.4">4.6.4</a>&nbsp;<a id="status.404" href="#status.404">404 Not Found</a></h3>
    19181930      <p id="rfc.section.4.6.4.p.1">The server has not found anything matching the effective request URI. No indication is given of whether the condition is temporary
     
    19211933         has been refused, or when no other response is applicable.
    19221934      </p>
    1923       <div id="rfc.iref.40"></div>
    1924       <div id="rfc.iref.s.22"></div>
     1935      <div id="rfc.iref.44"></div>
     1936      <div id="rfc.iref.s.26"></div>
    19251937      <h3 id="rfc.section.4.6.5"><a href="#rfc.section.4.6.5">4.6.5</a>&nbsp;<a id="status.405" href="#status.405">405 Method Not Allowed</a></h3>
    19261938      <p id="rfc.section.4.6.5.p.1">The method specified in the request-line is not allowed for the target resource. The response <em class="bcp14">MUST</em> include an Allow header field containing a list of valid methods for the requested resource.
    19271939      </p>
    1928       <div id="rfc.iref.41"></div>
    1929       <div id="rfc.iref.s.23"></div>
     1940      <div id="rfc.iref.45"></div>
     1941      <div id="rfc.iref.s.27"></div>
    19301942      <h3 id="rfc.section.4.6.6"><a href="#rfc.section.4.6.6">4.6.6</a>&nbsp;<a id="status.406" href="#status.406">406 Not Acceptable</a></h3>
    19311943      <p id="rfc.section.4.6.6.p.1">The resource identified by the request is only capable of generating response representations which have content characteristics
     
    19441956      <p id="rfc.section.4.6.6.p.4">If the response could be unacceptable, a user agent <em class="bcp14">SHOULD</em> temporarily stop receipt of more data and query the user for a decision on further actions.
    19451957      </p>
    1946       <div id="rfc.iref.42"></div>
    1947       <div id="rfc.iref.s.24"></div>
     1958      <div id="rfc.iref.46"></div>
     1959      <div id="rfc.iref.s.28"></div>
    19481960      <h3 id="rfc.section.4.6.7"><a href="#rfc.section.4.6.7">4.6.7</a>&nbsp;<a id="status.408" href="#status.408">408 Request Timeout</a></h3>
    19491961      <p id="rfc.section.4.6.7.p.1">The client did not produce a request within the time that the server was prepared to wait. The client <em class="bcp14">MAY</em> repeat the request without modifications at any later time.
    19501962      </p>
    1951       <div id="rfc.iref.43"></div>
    1952       <div id="rfc.iref.s.25"></div>
     1963      <div id="rfc.iref.47"></div>
     1964      <div id="rfc.iref.s.29"></div>
    19531965      <h3 id="rfc.section.4.6.8"><a href="#rfc.section.4.6.8">4.6.8</a>&nbsp;<a id="status.409" href="#status.409">409 Conflict</a></h3>
    19541966      <p id="rfc.section.4.6.8.p.1">The request could not be completed due to a conflict with the current state of the resource. This code is only allowed in
     
    19621974         contain a list of the differences between the two versions.
    19631975      </p>
    1964       <div id="rfc.iref.44"></div>
    1965       <div id="rfc.iref.s.26"></div>
     1976      <div id="rfc.iref.48"></div>
     1977      <div id="rfc.iref.s.30"></div>
    19661978      <h3 id="rfc.section.4.6.9"><a href="#rfc.section.4.6.9">4.6.9</a>&nbsp;<a id="status.410" href="#status.410">410 Gone</a></h3>
    19671979      <p id="rfc.section.4.6.9.p.1">The target resource is no longer available at the server and no forwarding address is known. This condition is expected to
     
    19771989      <p id="rfc.section.4.6.9.p.3">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.17"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 410 responses.
    19781990      </p>
    1979       <div id="rfc.iref.45"></div>
    1980       <div id="rfc.iref.s.27"></div>
     1991      <div id="rfc.iref.49"></div>
     1992      <div id="rfc.iref.s.31"></div>
    19811993      <h3 id="rfc.section.4.6.10"><a href="#rfc.section.4.6.10">4.6.10</a>&nbsp;<a id="status.411" href="#status.411">411 Length Required</a></h3>
    19821994      <p id="rfc.section.4.6.10.p.1">The server refuses to accept the request without a defined Content-Length. The client <em class="bcp14">MAY</em> repeat the request if it adds a valid Content-Length header field containing the length of the message body in the request
    19831995         message.
    19841996      </p>
    1985       <div id="rfc.iref.46"></div>
    1986       <div id="rfc.iref.s.28"></div>
     1997      <div id="rfc.iref.50"></div>
     1998      <div id="rfc.iref.s.32"></div>
    19871999      <h3 id="rfc.section.4.6.11"><a href="#rfc.section.4.6.11">4.6.11</a>&nbsp;<a id="status.413" href="#status.413">413 Request Representation Too Large</a></h3>
    19882000      <p id="rfc.section.4.6.11.p.1">The server is refusing to process a request because the request representation is larger than the server is willing or able
     
    19912003      <p id="rfc.section.4.6.11.p.2">If the condition is temporary, the server <em class="bcp14">SHOULD</em> include a Retry-After header field to indicate that it is temporary and after what time the client <em class="bcp14">MAY</em> try again.
    19922004      </p>
    1993       <div id="rfc.iref.47"></div>
    1994       <div id="rfc.iref.s.29"></div>
     2005      <div id="rfc.iref.51"></div>
     2006      <div id="rfc.iref.s.33"></div>
    19952007      <h3 id="rfc.section.4.6.12"><a href="#rfc.section.4.6.12">4.6.12</a>&nbsp;<a id="status.414" href="#status.414">414 URI Too Long</a></h3>
    19962008      <p id="rfc.section.4.6.12.p.1">The server is refusing to service the request because the effective request URI is longer than the server is willing to interpret.
     
    20002012         in some servers using fixed-length buffers for reading or manipulating the request-target.
    20012013      </p>
    2002       <div id="rfc.iref.48"></div>
    2003       <div id="rfc.iref.s.30"></div>
     2014      <div id="rfc.iref.52"></div>
     2015      <div id="rfc.iref.s.34"></div>
    20042016      <h3 id="rfc.section.4.6.13"><a href="#rfc.section.4.6.13">4.6.13</a>&nbsp;<a id="status.415" href="#status.415">415 Unsupported Media Type</a></h3>
    20052017      <p id="rfc.section.4.6.13.p.1">The server is refusing to service the request because the request payload is in a format not supported by this request method
    20062018         on the target resource.
    20072019      </p>
    2008       <div id="rfc.iref.49"></div>
    2009       <div id="rfc.iref.s.31"></div>
     2020      <div id="rfc.iref.53"></div>
     2021      <div id="rfc.iref.s.35"></div>
    20102022      <h3 id="rfc.section.4.6.14"><a href="#rfc.section.4.6.14">4.6.14</a>&nbsp;<a id="status.417" href="#status.417">417 Expectation Failed</a></h3>
    20112023      <p id="rfc.section.4.6.14.p.1">The expectation given in an Expect header field (see <a href="#header.expect" id="rfc.xref.header.expect.2" title="Expect">Section&nbsp;9.11</a>) could not be met by this server, or, if the server is a proxy, the server has unambiguous evidence that the request could
    20122024         not be met by the next-hop server.
    20132025      </p>
    2014       <div id="rfc.iref.50"></div>
    2015       <div id="rfc.iref.s.32"></div>
     2026      <div id="rfc.iref.54"></div>
     2027      <div id="rfc.iref.s.36"></div>
    20162028      <h3 id="rfc.section.4.6.15"><a href="#rfc.section.4.6.15">4.6.15</a>&nbsp;<a id="status.426" href="#status.426">426 Upgrade Required</a></h3>
    20172029      <p id="rfc.section.4.6.15.p.1">The request can not be completed without a prior protocol upgrade. This response <em class="bcp14">MUST</em> include an Upgrade header field (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 6.5</a> of <a href="#Part1" id="rfc.xref.Part1.36"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) specifying the required protocols.
     
    20292041      </p>
    20302042      <h2 id="rfc.section.4.7"><a href="#rfc.section.4.7">4.7</a>&nbsp;<a id="status.5xx" href="#status.5xx">Server Error 5xx</a></h2>
     2043      <div id="rfc.iref.55"></div>
     2044      <div id="rfc.iref.s.37"></div>
    20312045      <p id="rfc.section.4.7.p.1">Response status codes beginning with the digit "5" indicate cases in which the server is aware that it has erred or is incapable
    20322046         of performing the request. Except when responding to a HEAD request, the server <em class="bcp14">SHOULD</em> include a representation containing an explanation of the error situation, and whether it is a temporary or permanent condition.
    20332047         User agents <em class="bcp14">SHOULD</em> display any included representation to the user. These response codes are applicable to any request method.
    20342048      </p>
    2035       <div id="rfc.iref.51"></div>
    2036       <div id="rfc.iref.s.33"></div>
     2049      <div id="rfc.iref.56"></div>
     2050      <div id="rfc.iref.s.38"></div>
    20372051      <h3 id="rfc.section.4.7.1"><a href="#rfc.section.4.7.1">4.7.1</a>&nbsp;<a id="status.500" href="#status.500">500 Internal Server Error</a></h3>
    20382052      <p id="rfc.section.4.7.1.p.1">The server encountered an unexpected condition which prevented it from fulfilling the request.</p>
    2039       <div id="rfc.iref.52"></div>
    2040       <div id="rfc.iref.s.34"></div>
     2053      <div id="rfc.iref.57"></div>
     2054      <div id="rfc.iref.s.39"></div>
    20412055      <h3 id="rfc.section.4.7.2"><a href="#rfc.section.4.7.2">4.7.2</a>&nbsp;<a id="status.501" href="#status.501">501 Not Implemented</a></h3>
    20422056      <p id="rfc.section.4.7.2.p.1">The server does not support the functionality required to fulfill the request. This is the appropriate response when the server
    20432057         does not recognize the request method and is not capable of supporting it for any resource.
    20442058      </p>
    2045       <div id="rfc.iref.53"></div>
    2046       <div id="rfc.iref.s.35"></div>
     2059      <div id="rfc.iref.58"></div>
     2060      <div id="rfc.iref.s.40"></div>
    20472061      <h3 id="rfc.section.4.7.3"><a href="#rfc.section.4.7.3">4.7.3</a>&nbsp;<a id="status.502" href="#status.502">502 Bad Gateway</a></h3>
    20482062      <p id="rfc.section.4.7.3.p.1">The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting
    20492063         to fulfill the request.
    20502064      </p>
    2051       <div id="rfc.iref.54"></div>
    2052       <div id="rfc.iref.s.36"></div>
     2065      <div id="rfc.iref.59"></div>
     2066      <div id="rfc.iref.s.41"></div>
    20532067      <h3 id="rfc.section.4.7.4"><a href="#rfc.section.4.7.4">4.7.4</a>&nbsp;<a id="status.503" href="#status.503">503 Service Unavailable</a></h3>
    20542068      <p id="rfc.section.4.7.4.p.1">The server is currently unable to handle the request due to a temporary overloading or maintenance of the server.</p>
     
    20612075         </p>
    20622076      </div>
    2063       <div id="rfc.iref.55"></div>
    2064       <div id="rfc.iref.s.37"></div>
     2077      <div id="rfc.iref.60"></div>
     2078      <div id="rfc.iref.s.42"></div>
    20652079      <h3 id="rfc.section.4.7.5"><a href="#rfc.section.4.7.5">4.7.5</a>&nbsp;<a id="status.504" href="#status.504">504 Gateway Timeout</a></h3>
    20662080      <p id="rfc.section.4.7.5.p.1">The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server specified by the
     
    20712085         </p>
    20722086      </div>
    2073       <div id="rfc.iref.56"></div>
    2074       <div id="rfc.iref.s.38"></div>
     2087      <div id="rfc.iref.61"></div>
     2088      <div id="rfc.iref.s.43"></div>
    20752089      <h3 id="rfc.section.4.7.6"><a href="#rfc.section.4.7.6">4.7.6</a>&nbsp;<a id="status.505" href="#status.505">505 HTTP Version Not Supported</a></h3>
    20762090      <p id="rfc.section.4.7.6.p.1">The server does not support, or refuses to support, the protocol version that was used in the request message. The server
     
    29282942  <a href="#header.expect" class="smpl">expect-value</a> = <a href="#core.rules" class="smpl">token</a> / <a href="#core.rules" class="smpl">quoted-string</a>
    29292943</pre><p id="rfc.section.9.11.p.3">If all received Expect header field(s) are syntactically valid but contain an expectation that the recipient does not understand
    2930          or cannot comply with, the recipient <em class="bcp14">MUST</em> respond with a <a href="#status.417" class="smpl">417 (Expectation Failed)</a> status code. A recipient of a syntactically invalid Expectation header field <em class="bcp14">MUST</em> respond with a 4xx status code other than 417.
     2944         or cannot comply with, the recipient <em class="bcp14">MUST</em> respond with a <a href="#status.417" class="smpl">417 (Expectation Failed)</a> status code. A recipient of a syntactically invalid Expectation header field <em class="bcp14">MUST</em> respond with a <a href="#status.4xx" class="smpl">4xx</a> status code other than 417.
    29312945      </p>
    29322946      <p id="rfc.section.9.11.p.4">The only expectation defined by this specification is:</p>
    2933       <p id="rfc.section.9.11.p.5"><span id="rfc.iref.134"></span><span id="rfc.iref.e.2"></span> 100-continue
     2947      <p id="rfc.section.9.11.p.5"><span id="rfc.iref.139"></span><span id="rfc.iref.e.2"></span> 100-continue
    29342948      </p>
    29352949      <ul class="empty">
     
    29692983      </p>
    29702984      <div id="rfc.figure.u.50"></div><pre class="inline"><span id="rfc.iref.g.52"></span>  <a href="#header.location" class="smpl">Location</a> = <a href="#abnf.dependencies" class="smpl">URI-reference</a>
    2971 </pre><p id="rfc.section.9.13.p.3">For <a href="#status.201" class="smpl">201 (Created)</a> responses, the Location is the URI of the new resource which was created by the request. For 3xx responses, the location <em class="bcp14">SHOULD</em> indicate the server's preferred URI for automatic redirection to the resource.
     2985</pre><p id="rfc.section.9.13.p.3">For <a href="#status.201" class="smpl">201 (Created)</a> responses, the Location is the URI of the new resource which was created by the request. For <a href="#status.3xx" class="smpl">3xx</a> responses, the location <em class="bcp14">SHOULD</em> indicate the server's preferred URI for automatic redirection to the resource.
    29722986      </p>
    29732987      <p id="rfc.section.9.13.p.4">The field value consists of a single URI-reference. When it has the form of a relative reference (<a href="#RFC3986" id="rfc.xref.RFC3986.1"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-4.2">Section 4.2</a>), the final value is computed by resolving it against the effective request URI (<a href="#RFC3986" id="rfc.xref.RFC3986.2"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-5">Section 5</a>). If the original URI, as navigated to by the user agent, did contain a fragment identifier, and the final value does not,
     
    30293043      <h2 id="rfc.section.9.16"><a href="#rfc.section.9.16">9.16</a>&nbsp;<a id="header.retry-after" href="#header.retry-after">Retry-After</a></h2>
    30303044      <p id="rfc.section.9.16.p.1">The header "Retry-After" field can be used with a <a href="#status.503" class="smpl">503 (Service
    3031             Unavailable)</a> response to indicate how long the service is expected to be unavailable to the requesting client. This field <em class="bcp14">MAY</em> also be used with any 3xx (Redirection) response to indicate the minimum time the user-agent is asked to wait before issuing
    3032          the redirected request.
     3045            Unavailable)</a> response to indicate how long the service is expected to be unavailable to the requesting client. This field <em class="bcp14">MAY</em> also be used with any <a href="#status.3xx" class="smpl">3xx (Redirection)</a> response to indicate the minimum time the user-agent is asked to wait before issuing the redirected request.
    30333046      </p>
    30343047      <p id="rfc.section.9.16.p.2">The value of this field can be either an HTTP-date or an integer number of seconds (in decimal) after the time of the response.</p>
     
    30423055  Retry-After: 120
    30433056</pre><p id="rfc.section.9.16.p.8">In the latter example, the delay is 2 minutes.</p>
    3044       <div id="rfc.iref.s.39"></div>
     3057      <div id="rfc.iref.s.44"></div>
    30453058      <div id="rfc.iref.h.18"></div>
    30463059      <h2 id="rfc.section.9.17"><a href="#rfc.section.9.17">9.17</a>&nbsp;<a id="header.server" href="#header.server">Server</a></h2>
     
    39473960      <p id="rfc.section.C.p.5">Broadened the definition of <a href="#status.203" class="smpl">203 (Non-Authoritative Information)</a> to include cases of payload transformations as well. (<a href="#status.203" id="rfc.xref.status.203.3" title="203 Non-Authoritative Information">Section&nbsp;4.4.4</a>)
    39483961      </p>
    3949       <p id="rfc.section.C.p.6">Status codes 301, 302, and 307: removed the normative requirements on both response payloads and user interaction. (<a href="#status.3xx" title="Redirection 3xx">Section&nbsp;4.5</a>)
     3962      <p id="rfc.section.C.p.6">Status codes 301, 302, and 307: removed the normative requirements on both response payloads and user interaction. (<a href="#status.3xx" id="rfc.xref.status.3xx.1" title="Redirection 3xx">Section&nbsp;4.5</a>)
    39503963      </p>
    39513964      <p id="rfc.section.C.p.7">Failed to consider that there are many other request methods that are safe to automatically redirect, and further that the
     
    44334446      <p id="rfc.section.E.18.p.1">Closed issues: </p>
    44344447      <ul>
    4435          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/10">http://tools.ietf.org/wg/httpbis/trac/ticket/10</a>&gt;: "Safe Methods vs Redirection" (we missed the introduction to the 3xx status codes when fixing this previously)
     4448         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/10">http://tools.ietf.org/wg/httpbis/trac/ticket/10</a>&gt;: "Safe Methods vs Redirection" (we missed the introduction to the <a href="#status.3xx" class="smpl">3xx</a> status codes when fixing this previously)
    44364449         </li>
    44374450      </ul>
     
    47224735         <ul class="ind">
    47234736            <li><a id="rfc.index.1" href="#rfc.index.1"><b>1</b></a><ul>
    4724                   <li>100 Continue (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.100.1">4.1</a>, <a href="#rfc.iref.21"><b>4.3.1</b></a>, <a href="#rfc.xref.status.100.2">10.2</a></li>
    4725                   <li>100-continue (expect value)&nbsp;&nbsp;<a href="#rfc.iref.134"><b>9.11</b></a></li>
    4726                   <li>101 Switching Protocols (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.101.1">4.1</a>, <a href="#rfc.iref.22"><b>4.3.2</b></a>, <a href="#rfc.xref.status.101.2">10.2</a></li>
     4737                  <li>100 Continue (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.100.1">4.1</a>, <a href="#rfc.iref.22"><b>4.3.1</b></a>, <a href="#rfc.xref.status.100.2">10.2</a></li>
     4738                  <li>100-continue (expect value)&nbsp;&nbsp;<a href="#rfc.iref.139"><b>9.11</b></a></li>
     4739                  <li>101 Switching Protocols (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.101.1">4.1</a>, <a href="#rfc.iref.23"><b>4.3.2</b></a>, <a href="#rfc.xref.status.101.2">10.2</a></li>
     4740                  <li>1xx Informational (status code class)&nbsp;&nbsp;<a href="#rfc.iref.21"><b>4.3</b></a></li>
    47274741               </ul>
    47284742            </li>
    47294743            <li><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul>
    4730                   <li>200 OK (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.200.1">4.1</a>, <a href="#rfc.iref.23"><b>4.4.1</b></a>, <a href="#rfc.xref.status.200.2">10.2</a></li>
    4731                   <li>201 Created (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.201.1">4.1</a>, <a href="#rfc.iref.24"><b>4.4.2</b></a>, <a href="#rfc.xref.status.201.2">10.2</a></li>
    4732                   <li>202 Accepted (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.202.1">4.1</a>, <a href="#rfc.iref.25"><b>4.4.3</b></a>, <a href="#rfc.xref.status.202.2">10.2</a></li>
    4733                   <li>203 Non-Authoritative Information (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.203.1">4.1</a>, <a href="#rfc.iref.26"><b>4.4.4</b></a>, <a href="#rfc.xref.status.203.2">10.2</a>, <a href="#rfc.xref.status.203.3">C</a></li>
    4734                   <li>204 No Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.204.1">4.1</a>, <a href="#rfc.iref.27"><b>4.4.5</b></a>, <a href="#rfc.xref.status.204.2">10.2</a></li>
    4735                   <li>205 Reset Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.205.1">4.1</a>, <a href="#rfc.iref.28"><b>4.4.6</b></a>, <a href="#rfc.xref.status.205.2">10.2</a></li>
     4744                  <li>200 OK (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.200.1">4.1</a>, <a href="#rfc.iref.25"><b>4.4.1</b></a>, <a href="#rfc.xref.status.200.2">10.2</a></li>
     4745                  <li>201 Created (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.201.1">4.1</a>, <a href="#rfc.iref.26"><b>4.4.2</b></a>, <a href="#rfc.xref.status.201.2">10.2</a></li>
     4746                  <li>202 Accepted (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.202.1">4.1</a>, <a href="#rfc.iref.27"><b>4.4.3</b></a>, <a href="#rfc.xref.status.202.2">10.2</a></li>
     4747                  <li>203 Non-Authoritative Information (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.203.1">4.1</a>, <a href="#rfc.iref.28"><b>4.4.4</b></a>, <a href="#rfc.xref.status.203.2">10.2</a>, <a href="#rfc.xref.status.203.3">C</a></li>
     4748                  <li>204 No Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.204.1">4.1</a>, <a href="#rfc.iref.29"><b>4.4.5</b></a>, <a href="#rfc.xref.status.204.2">10.2</a></li>
     4749                  <li>205 Reset Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.205.1">4.1</a>, <a href="#rfc.iref.30"><b>4.4.6</b></a>, <a href="#rfc.xref.status.205.2">10.2</a></li>
     4750                  <li>2xx Successful (status code class)&nbsp;&nbsp;<a href="#rfc.iref.24"><b>4.4</b></a></li>
    47364751               </ul>
    47374752            </li>
    47384753            <li><a id="rfc.index.3" href="#rfc.index.3"><b>3</b></a><ul>
    4739                   <li>300 Multiple Choices (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.300.1">4.1</a>, <a href="#rfc.iref.29"><b>4.5.1</b></a>, <a href="#rfc.xref.status.300.2">10.2</a></li>
    4740                   <li>301 Moved Permanently (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.301.1">4.1</a>, <a href="#rfc.iref.30"><b>4.5.2</b></a>, <a href="#rfc.xref.status.301.2">10.2</a>, <a href="#rfc.xref.status.301.3">C</a></li>
    4741                   <li>302 Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.302.1">4.1</a>, <a href="#rfc.iref.31"><b>4.5.3</b></a>, <a href="#rfc.xref.status.302.2">10.2</a>, <a href="#rfc.xref.status.302.3">C</a></li>
    4742                   <li>303 See Other (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.303.1">4.1</a>, <a href="#rfc.iref.32"><b>4.5.4</b></a>, <a href="#rfc.xref.status.303.2">10.2</a></li>
    4743                   <li>305 Use Proxy (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.305.1">4.1</a>, <a href="#rfc.iref.33"><b>4.5.5</b></a>, <a href="#rfc.xref.status.305.2">10.2</a>, <a href="#rfc.xref.status.305.3">C</a></li>
    4744                   <li>306 (Unused) (status code)&nbsp;&nbsp;<a href="#rfc.iref.34"><b>4.5.6</b></a>, <a href="#rfc.xref.status.306.1">10.2</a></li>
    4745                   <li>307 Temporary Redirect (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.307.1">4.1</a>, <a href="#rfc.iref.35"><b>4.5.7</b></a>, <a href="#rfc.xref.status.307.2">10.2</a>, <a href="#rfc.xref.status.307.3">C</a></li>
     4754                  <li>300 Multiple Choices (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.300.1">4.1</a>, <a href="#rfc.iref.32"><b>4.5.1</b></a>, <a href="#rfc.xref.status.300.2">10.2</a></li>
     4755                  <li>301 Moved Permanently (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.301.1">4.1</a>, <a href="#rfc.iref.33"><b>4.5.2</b></a>, <a href="#rfc.xref.status.301.2">10.2</a>, <a href="#rfc.xref.status.301.3">C</a></li>
     4756                  <li>302 Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.302.1">4.1</a>, <a href="#rfc.iref.34"><b>4.5.3</b></a>, <a href="#rfc.xref.status.302.2">10.2</a>, <a href="#rfc.xref.status.302.3">C</a></li>
     4757                  <li>303 See Other (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.303.1">4.1</a>, <a href="#rfc.iref.35"><b>4.5.4</b></a>, <a href="#rfc.xref.status.303.2">10.2</a></li>
     4758                  <li>305 Use Proxy (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.305.1">4.1</a>, <a href="#rfc.iref.36"><b>4.5.5</b></a>, <a href="#rfc.xref.status.305.2">10.2</a>, <a href="#rfc.xref.status.305.3">C</a></li>
     4759                  <li>306 (Unused) (status code)&nbsp;&nbsp;<a href="#rfc.iref.37"><b>4.5.6</b></a>, <a href="#rfc.xref.status.306.1">10.2</a></li>
     4760                  <li>307 Temporary Redirect (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.307.1">4.1</a>, <a href="#rfc.iref.38"><b>4.5.7</b></a>, <a href="#rfc.xref.status.307.2">10.2</a>, <a href="#rfc.xref.status.307.3">C</a></li>
     4761                  <li>3xx Redirection (status code class)&nbsp;&nbsp;<a href="#rfc.iref.31"><b>4.5</b></a>, <a href="#rfc.xref.status.3xx.1">C</a></li>
    47464762               </ul>
    47474763            </li>
    47484764            <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul>
    4749                   <li>400 Bad Request (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.400.1">4.1</a>, <a href="#rfc.iref.36"><b>4.6.1</b></a>, <a href="#rfc.xref.status.400.2">10.2</a></li>
    4750                   <li>402 Payment Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.402.1">4.1</a>, <a href="#rfc.iref.37"><b>4.6.2</b></a>, <a href="#rfc.xref.status.402.2">10.2</a></li>
    4751                   <li>403 Forbidden (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.403.1">4.1</a>, <a href="#rfc.iref.38"><b>4.6.3</b></a>, <a href="#rfc.xref.status.403.2">10.2</a></li>
    4752                   <li>404 Not Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.404.1">4.1</a>, <a href="#rfc.iref.39"><b>4.6.4</b></a>, <a href="#rfc.xref.status.404.2">10.2</a></li>
    4753                   <li>405 Method Not Allowed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.405.1">4.1</a>, <a href="#rfc.iref.40"><b>4.6.5</b></a>, <a href="#rfc.xref.status.405.2">10.2</a></li>
    4754                   <li>406 Not Acceptable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.406.1">4.1</a>, <a href="#rfc.iref.41"><b>4.6.6</b></a>, <a href="#rfc.xref.status.406.2">10.2</a></li>
    4755                   <li>408 Request Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.408.1">4.1</a>, <a href="#rfc.iref.42"><b>4.6.7</b></a>, <a href="#rfc.xref.status.408.2">10.2</a></li>
    4756                   <li>409 Conflict (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.409.1">4.1</a>, <a href="#rfc.iref.43"><b>4.6.8</b></a>, <a href="#rfc.xref.status.409.2">10.2</a></li>
    4757                   <li>410 Gone (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.410.1">4.1</a>, <a href="#rfc.iref.44"><b>4.6.9</b></a>, <a href="#rfc.xref.status.410.2">10.2</a></li>
    4758                   <li>411 Length Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.411.1">4.1</a>, <a href="#rfc.iref.45"><b>4.6.10</b></a>, <a href="#rfc.xref.status.411.2">10.2</a></li>
    4759                   <li>413 Request Representation Too Large (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.413.1">4.1</a>, <a href="#rfc.iref.46"><b>4.6.11</b></a>, <a href="#rfc.xref.status.413.2">10.2</a></li>
    4760                   <li>414 URI Too Long (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.414.1">4.1</a>, <a href="#rfc.iref.47"><b>4.6.12</b></a>, <a href="#rfc.xref.status.414.2">10.2</a></li>
    4761                   <li>415 Unsupported Media Type (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.415.1">4.1</a>, <a href="#rfc.iref.48"><b>4.6.13</b></a>, <a href="#rfc.xref.status.415.2">10.2</a></li>
    4762                   <li>417 Expectation Failed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.417.1">4.1</a>, <a href="#rfc.iref.49"><b>4.6.14</b></a>, <a href="#rfc.xref.status.417.2">10.2</a></li>
    4763                   <li>426 Upgrade Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.426.1">4.1</a>, <a href="#rfc.iref.50"><b>4.6.15</b></a>, <a href="#rfc.xref.status.426.2">10.2</a>, <a href="#rfc.xref.status.426.3">C</a></li>
     4765                  <li>400 Bad Request (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.400.1">4.1</a>, <a href="#rfc.iref.40"><b>4.6.1</b></a>, <a href="#rfc.xref.status.400.2">10.2</a></li>
     4766                  <li>402 Payment Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.402.1">4.1</a>, <a href="#rfc.iref.41"><b>4.6.2</b></a>, <a href="#rfc.xref.status.402.2">10.2</a></li>
     4767                  <li>403 Forbidden (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.403.1">4.1</a>, <a href="#rfc.iref.42"><b>4.6.3</b></a>, <a href="#rfc.xref.status.403.2">10.2</a></li>
     4768                  <li>404 Not Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.404.1">4.1</a>, <a href="#rfc.iref.43"><b>4.6.4</b></a>, <a href="#rfc.xref.status.404.2">10.2</a></li>
     4769                  <li>405 Method Not Allowed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.405.1">4.1</a>, <a href="#rfc.iref.44"><b>4.6.5</b></a>, <a href="#rfc.xref.status.405.2">10.2</a></li>
     4770                  <li>406 Not Acceptable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.406.1">4.1</a>, <a href="#rfc.iref.45"><b>4.6.6</b></a>, <a href="#rfc.xref.status.406.2">10.2</a></li>
     4771                  <li>408 Request Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.408.1">4.1</a>, <a href="#rfc.iref.46"><b>4.6.7</b></a>, <a href="#rfc.xref.status.408.2">10.2</a></li>
     4772                  <li>409 Conflict (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.409.1">4.1</a>, <a href="#rfc.iref.47"><b>4.6.8</b></a>, <a href="#rfc.xref.status.409.2">10.2</a></li>
     4773                  <li>410 Gone (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.410.1">4.1</a>, <a href="#rfc.iref.48"><b>4.6.9</b></a>, <a href="#rfc.xref.status.410.2">10.2</a></li>
     4774                  <li>411 Length Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.411.1">4.1</a>, <a href="#rfc.iref.49"><b>4.6.10</b></a>, <a href="#rfc.xref.status.411.2">10.2</a></li>
     4775                  <li>413 Request Representation Too Large (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.413.1">4.1</a>, <a href="#rfc.iref.50"><b>4.6.11</b></a>, <a href="#rfc.xref.status.413.2">10.2</a></li>
     4776                  <li>414 URI Too Long (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.414.1">4.1</a>, <a href="#rfc.iref.51"><b>4.6.12</b></a>, <a href="#rfc.xref.status.414.2">10.2</a></li>
     4777                  <li>415 Unsupported Media Type (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.415.1">4.1</a>, <a href="#rfc.iref.52"><b>4.6.13</b></a>, <a href="#rfc.xref.status.415.2">10.2</a></li>
     4778                  <li>417 Expectation Failed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.417.1">4.1</a>, <a href="#rfc.iref.53"><b>4.6.14</b></a>, <a href="#rfc.xref.status.417.2">10.2</a></li>
     4779                  <li>426 Upgrade Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.426.1">4.1</a>, <a href="#rfc.iref.54"><b>4.6.15</b></a>, <a href="#rfc.xref.status.426.2">10.2</a>, <a href="#rfc.xref.status.426.3">C</a></li>
     4780                  <li>4xx Client Error (status code class)&nbsp;&nbsp;<a href="#rfc.iref.39"><b>4.6</b></a></li>
    47644781               </ul>
    47654782            </li>
    47664783            <li><a id="rfc.index.5" href="#rfc.index.5"><b>5</b></a><ul>
    4767                   <li>500 Internal Server Error (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.500.1">4.1</a>, <a href="#rfc.iref.51"><b>4.7.1</b></a>, <a href="#rfc.xref.status.500.2">10.2</a></li>
    4768                   <li>501 Not Implemented (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.501.1">4.1</a>, <a href="#rfc.iref.52"><b>4.7.2</b></a>, <a href="#rfc.xref.status.501.2">10.2</a></li>
    4769                   <li>502 Bad Gateway (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.502.1">4.1</a>, <a href="#rfc.iref.53"><b>4.7.3</b></a>, <a href="#rfc.xref.status.502.2">10.2</a></li>
    4770                   <li>503 Service Unavailable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.503.1">4.1</a>, <a href="#rfc.iref.54"><b>4.7.4</b></a>, <a href="#rfc.xref.status.503.2">10.2</a></li>
    4771                   <li>504 Gateway Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.504.1">4.1</a>, <a href="#rfc.iref.55"><b>4.7.5</b></a>, <a href="#rfc.xref.status.504.2">10.2</a></li>
    4772                   <li>505 HTTP Version Not Supported (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.505.1">4.1</a>, <a href="#rfc.iref.56"><b>4.7.6</b></a>, <a href="#rfc.xref.status.505.2">10.2</a></li>
     4784                  <li>500 Internal Server Error (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.500.1">4.1</a>, <a href="#rfc.iref.56"><b>4.7.1</b></a>, <a href="#rfc.xref.status.500.2">10.2</a></li>
     4785                  <li>501 Not Implemented (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.501.1">4.1</a>, <a href="#rfc.iref.57"><b>4.7.2</b></a>, <a href="#rfc.xref.status.501.2">10.2</a></li>
     4786                  <li>502 Bad Gateway (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.502.1">4.1</a>, <a href="#rfc.iref.58"><b>4.7.3</b></a>, <a href="#rfc.xref.status.502.2">10.2</a></li>
     4787                  <li>503 Service Unavailable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.503.1">4.1</a>, <a href="#rfc.iref.59"><b>4.7.4</b></a>, <a href="#rfc.xref.status.503.2">10.2</a></li>
     4788                  <li>504 Gateway Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.504.1">4.1</a>, <a href="#rfc.iref.60"><b>4.7.5</b></a>, <a href="#rfc.xref.status.504.2">10.2</a></li>
     4789                  <li>505 HTTP Version Not Supported (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.505.1">4.1</a>, <a href="#rfc.iref.61"><b>4.7.6</b></a>, <a href="#rfc.xref.status.505.2">10.2</a></li>
     4790                  <li>5xx Server Error (status code class)&nbsp;&nbsp;<a href="#rfc.iref.55"><b>4.7</b></a></li>
    47734791               </ul>
    47744792            </li>
     
    51175135                  <li>Safe Methods&nbsp;&nbsp;<a href="#rfc.iref.s.2"><b>2.1.1</b></a></li>
    51185136                  <li>selected representation&nbsp;&nbsp;<a href="#rfc.iref.s.1"><b>1.1</b></a></li>
    5119                   <li>Server header field&nbsp;&nbsp;<a href="#rfc.xref.header.server.1">3.3</a>, <a href="#rfc.iref.s.39"><b>9.17</b></a>, <a href="#rfc.xref.header.server.2">10.3</a>, <a href="#rfc.xref.header.server.3">11.1</a>, <a href="#rfc.xref.header.server.4">C</a></li>
     5137                  <li>Server header field&nbsp;&nbsp;<a href="#rfc.xref.header.server.1">3.3</a>, <a href="#rfc.iref.s.44"><b>9.17</b></a>, <a href="#rfc.xref.header.server.2">10.3</a>, <a href="#rfc.xref.header.server.3">11.1</a>, <a href="#rfc.xref.header.server.4">C</a></li>
    51205138                  <li>Status Codes&nbsp;&nbsp;
    51215139                     <ul>
    5122                         <li>100 Continue&nbsp;&nbsp;<a href="#rfc.xref.status.100.1">4.1</a>, <a href="#rfc.iref.s.3"><b>4.3.1</b></a>, <a href="#rfc.xref.status.100.2">10.2</a></li>
    5123                         <li>101 Switching Protocols&nbsp;&nbsp;<a href="#rfc.xref.status.101.1">4.1</a>, <a href="#rfc.iref.s.4"><b>4.3.2</b></a>, <a href="#rfc.xref.status.101.2">10.2</a></li>
    5124                         <li>200 OK&nbsp;&nbsp;<a href="#rfc.xref.status.200.1">4.1</a>, <a href="#rfc.iref.s.5"><b>4.4.1</b></a>, <a href="#rfc.xref.status.200.2">10.2</a></li>
    5125                         <li>201 Created&nbsp;&nbsp;<a href="#rfc.xref.status.201.1">4.1</a>, <a href="#rfc.iref.s.6"><b>4.4.2</b></a>, <a href="#rfc.xref.status.201.2">10.2</a></li>
    5126                         <li>202 Accepted&nbsp;&nbsp;<a href="#rfc.xref.status.202.1">4.1</a>, <a href="#rfc.iref.s.7"><b>4.4.3</b></a>, <a href="#rfc.xref.status.202.2">10.2</a></li>
    5127                         <li>203 Non-Authoritative Information&nbsp;&nbsp;<a href="#rfc.xref.status.203.1">4.1</a>, <a href="#rfc.iref.s.8"><b>4.4.4</b></a>, <a href="#rfc.xref.status.203.2">10.2</a>, <a href="#rfc.xref.status.203.3">C</a></li>
    5128                         <li>204 No Content&nbsp;&nbsp;<a href="#rfc.xref.status.204.1">4.1</a>, <a href="#rfc.iref.s.9"><b>4.4.5</b></a>, <a href="#rfc.xref.status.204.2">10.2</a></li>
    5129                         <li>205 Reset Content&nbsp;&nbsp;<a href="#rfc.xref.status.205.1">4.1</a>, <a href="#rfc.iref.s.10"><b>4.4.6</b></a>, <a href="#rfc.xref.status.205.2">10.2</a></li>
    5130                         <li>300 Multiple Choices&nbsp;&nbsp;<a href="#rfc.xref.status.300.1">4.1</a>, <a href="#rfc.iref.s.11"><b>4.5.1</b></a>, <a href="#rfc.xref.status.300.2">10.2</a></li>
    5131                         <li>301 Moved Permanently&nbsp;&nbsp;<a href="#rfc.xref.status.301.1">4.1</a>, <a href="#rfc.iref.s.12"><b>4.5.2</b></a>, <a href="#rfc.xref.status.301.2">10.2</a>, <a href="#rfc.xref.status.301.3">C</a></li>
    5132                         <li>302 Found&nbsp;&nbsp;<a href="#rfc.xref.status.302.1">4.1</a>, <a href="#rfc.iref.s.13"><b>4.5.3</b></a>, <a href="#rfc.xref.status.302.2">10.2</a>, <a href="#rfc.xref.status.302.3">C</a></li>
    5133                         <li>303 See Other&nbsp;&nbsp;<a href="#rfc.xref.status.303.1">4.1</a>, <a href="#rfc.iref.s.14"><b>4.5.4</b></a>, <a href="#rfc.xref.status.303.2">10.2</a></li>
    5134                         <li>305 Use Proxy&nbsp;&nbsp;<a href="#rfc.xref.status.305.1">4.1</a>, <a href="#rfc.iref.s.15"><b>4.5.5</b></a>, <a href="#rfc.xref.status.305.2">10.2</a>, <a href="#rfc.xref.status.305.3">C</a></li>
    5135                         <li>306 (Unused)&nbsp;&nbsp;<a href="#rfc.iref.s.16"><b>4.5.6</b></a>, <a href="#rfc.xref.status.306.1">10.2</a></li>
    5136                         <li>307 Temporary Redirect&nbsp;&nbsp;<a href="#rfc.xref.status.307.1">4.1</a>, <a href="#rfc.iref.s.17"><b>4.5.7</b></a>, <a href="#rfc.xref.status.307.2">10.2</a>, <a href="#rfc.xref.status.307.3">C</a></li>
    5137                         <li>400 Bad Request&nbsp;&nbsp;<a href="#rfc.xref.status.400.1">4.1</a>, <a href="#rfc.iref.s.18"><b>4.6.1</b></a>, <a href="#rfc.xref.status.400.2">10.2</a></li>
    5138                         <li>402 Payment Required&nbsp;&nbsp;<a href="#rfc.xref.status.402.1">4.1</a>, <a href="#rfc.iref.s.19"><b>4.6.2</b></a>, <a href="#rfc.xref.status.402.2">10.2</a></li>
    5139                         <li>403 Forbidden&nbsp;&nbsp;<a href="#rfc.xref.status.403.1">4.1</a>, <a href="#rfc.iref.s.20"><b>4.6.3</b></a>, <a href="#rfc.xref.status.403.2">10.2</a></li>
    5140                         <li>404 Not Found&nbsp;&nbsp;<a href="#rfc.xref.status.404.1">4.1</a>, <a href="#rfc.iref.s.21"><b>4.6.4</b></a>, <a href="#rfc.xref.status.404.2">10.2</a></li>
    5141                         <li>405 Method Not Allowed&nbsp;&nbsp;<a href="#rfc.xref.status.405.1">4.1</a>, <a href="#rfc.iref.s.22"><b>4.6.5</b></a>, <a href="#rfc.xref.status.405.2">10.2</a></li>
    5142                         <li>406 Not Acceptable&nbsp;&nbsp;<a href="#rfc.xref.status.406.1">4.1</a>, <a href="#rfc.iref.s.23"><b>4.6.6</b></a>, <a href="#rfc.xref.status.406.2">10.2</a></li>
    5143                         <li>408 Request Timeout&nbsp;&nbsp;<a href="#rfc.xref.status.408.1">4.1</a>, <a href="#rfc.iref.s.24"><b>4.6.7</b></a>, <a href="#rfc.xref.status.408.2">10.2</a></li>
    5144                         <li>409 Conflict&nbsp;&nbsp;<a href="#rfc.xref.status.409.1">4.1</a>, <a href="#rfc.iref.s.25"><b>4.6.8</b></a>, <a href="#rfc.xref.status.409.2">10.2</a></li>
    5145                         <li>410 Gone&nbsp;&nbsp;<a href="#rfc.xref.status.410.1">4.1</a>, <a href="#rfc.iref.s.26"><b>4.6.9</b></a>, <a href="#rfc.xref.status.410.2">10.2</a></li>
    5146                         <li>411 Length Required&nbsp;&nbsp;<a href="#rfc.xref.status.411.1">4.1</a>, <a href="#rfc.iref.s.27"><b>4.6.10</b></a>, <a href="#rfc.xref.status.411.2">10.2</a></li>
    5147                         <li>413 Request Representation Too Large&nbsp;&nbsp;<a href="#rfc.xref.status.413.1">4.1</a>, <a href="#rfc.iref.s.28"><b>4.6.11</b></a>, <a href="#rfc.xref.status.413.2">10.2</a></li>
    5148                         <li>414 URI Too Long&nbsp;&nbsp;<a href="#rfc.xref.status.414.1">4.1</a>, <a href="#rfc.iref.s.29"><b>4.6.12</b></a>, <a href="#rfc.xref.status.414.2">10.2</a></li>
    5149                         <li>415 Unsupported Media Type&nbsp;&nbsp;<a href="#rfc.xref.status.415.1">4.1</a>, <a href="#rfc.iref.s.30"><b>4.6.13</b></a>, <a href="#rfc.xref.status.415.2">10.2</a></li>
    5150                         <li>417 Expectation Failed&nbsp;&nbsp;<a href="#rfc.xref.status.417.1">4.1</a>, <a href="#rfc.iref.s.31"><b>4.6.14</b></a>, <a href="#rfc.xref.status.417.2">10.2</a></li>
    5151                         <li>426 Upgrade Required&nbsp;&nbsp;<a href="#rfc.xref.status.426.1">4.1</a>, <a href="#rfc.iref.s.32"><b>4.6.15</b></a>, <a href="#rfc.xref.status.426.2">10.2</a>, <a href="#rfc.xref.status.426.3">C</a></li>
    5152                         <li>500 Internal Server Error&nbsp;&nbsp;<a href="#rfc.xref.status.500.1">4.1</a>, <a href="#rfc.iref.s.33"><b>4.7.1</b></a>, <a href="#rfc.xref.status.500.2">10.2</a></li>
    5153                         <li>501 Not Implemented&nbsp;&nbsp;<a href="#rfc.xref.status.501.1">4.1</a>, <a href="#rfc.iref.s.34"><b>4.7.2</b></a>, <a href="#rfc.xref.status.501.2">10.2</a></li>
    5154                         <li>502 Bad Gateway&nbsp;&nbsp;<a href="#rfc.xref.status.502.1">4.1</a>, <a href="#rfc.iref.s.35"><b>4.7.3</b></a>, <a href="#rfc.xref.status.502.2">10.2</a></li>
    5155                         <li>503 Service Unavailable&nbsp;&nbsp;<a href="#rfc.xref.status.503.1">4.1</a>, <a href="#rfc.iref.s.36"><b>4.7.4</b></a>, <a href="#rfc.xref.status.503.2">10.2</a></li>
    5156                         <li>504 Gateway Timeout&nbsp;&nbsp;<a href="#rfc.xref.status.504.1">4.1</a>, <a href="#rfc.iref.s.37"><b>4.7.5</b></a>, <a href="#rfc.xref.status.504.2">10.2</a></li>
    5157                         <li>505 HTTP Version Not Supported&nbsp;&nbsp;<a href="#rfc.xref.status.505.1">4.1</a>, <a href="#rfc.iref.s.38"><b>4.7.6</b></a>, <a href="#rfc.xref.status.505.2">10.2</a></li>
     5140                        <li>100 Continue&nbsp;&nbsp;<a href="#rfc.xref.status.100.1">4.1</a>, <a href="#rfc.iref.s.4"><b>4.3.1</b></a>, <a href="#rfc.xref.status.100.2">10.2</a></li>
     5141                        <li>101 Switching Protocols&nbsp;&nbsp;<a href="#rfc.xref.status.101.1">4.1</a>, <a href="#rfc.iref.s.5"><b>4.3.2</b></a>, <a href="#rfc.xref.status.101.2">10.2</a></li>
     5142                        <li>200 OK&nbsp;&nbsp;<a href="#rfc.xref.status.200.1">4.1</a>, <a href="#rfc.iref.s.7"><b>4.4.1</b></a>, <a href="#rfc.xref.status.200.2">10.2</a></li>
     5143                        <li>201 Created&nbsp;&nbsp;<a href="#rfc.xref.status.201.1">4.1</a>, <a href="#rfc.iref.s.8"><b>4.4.2</b></a>, <a href="#rfc.xref.status.201.2">10.2</a></li>
     5144                        <li>202 Accepted&nbsp;&nbsp;<a href="#rfc.xref.status.202.1">4.1</a>, <a href="#rfc.iref.s.9"><b>4.4.3</b></a>, <a href="#rfc.xref.status.202.2">10.2</a></li>
     5145                        <li>203 Non-Authoritative Information&nbsp;&nbsp;<a href="#rfc.xref.status.203.1">4.1</a>, <a href="#rfc.iref.s.10"><b>4.4.4</b></a>, <a href="#rfc.xref.status.203.2">10.2</a>, <a href="#rfc.xref.status.203.3">C</a></li>
     5146                        <li>204 No Content&nbsp;&nbsp;<a href="#rfc.xref.status.204.1">4.1</a>, <a href="#rfc.iref.s.11"><b>4.4.5</b></a>, <a href="#rfc.xref.status.204.2">10.2</a></li>
     5147                        <li>205 Reset Content&nbsp;&nbsp;<a href="#rfc.xref.status.205.1">4.1</a>, <a href="#rfc.iref.s.12"><b>4.4.6</b></a>, <a href="#rfc.xref.status.205.2">10.2</a></li>
     5148                        <li>300 Multiple Choices&nbsp;&nbsp;<a href="#rfc.xref.status.300.1">4.1</a>, <a href="#rfc.iref.s.14"><b>4.5.1</b></a>, <a href="#rfc.xref.status.300.2">10.2</a></li>
     5149                        <li>301 Moved Permanently&nbsp;&nbsp;<a href="#rfc.xref.status.301.1">4.1</a>, <a href="#rfc.iref.s.15"><b>4.5.2</b></a>, <a href="#rfc.xref.status.301.2">10.2</a>, <a href="#rfc.xref.status.301.3">C</a></li>
     5150                        <li>302 Found&nbsp;&nbsp;<a href="#rfc.xref.status.302.1">4.1</a>, <a href="#rfc.iref.s.16"><b>4.5.3</b></a>, <a href="#rfc.xref.status.302.2">10.2</a>, <a href="#rfc.xref.status.302.3">C</a></li>
     5151                        <li>303 See Other&nbsp;&nbsp;<a href="#rfc.xref.status.303.1">4.1</a>, <a href="#rfc.iref.s.17"><b>4.5.4</b></a>, <a href="#rfc.xref.status.303.2">10.2</a></li>
     5152                        <li>305 Use Proxy&nbsp;&nbsp;<a href="#rfc.xref.status.305.1">4.1</a>, <a href="#rfc.iref.s.18"><b>4.5.5</b></a>, <a href="#rfc.xref.status.305.2">10.2</a>, <a href="#rfc.xref.status.305.3">C</a></li>
     5153                        <li>306 (Unused)&nbsp;&nbsp;<a href="#rfc.iref.s.19"><b>4.5.6</b></a>, <a href="#rfc.xref.status.306.1">10.2</a></li>
     5154                        <li>307 Temporary Redirect&nbsp;&nbsp;<a href="#rfc.xref.status.307.1">4.1</a>, <a href="#rfc.iref.s.20"><b>4.5.7</b></a>, <a href="#rfc.xref.status.307.2">10.2</a>, <a href="#rfc.xref.status.307.3">C</a></li>
     5155                        <li>400 Bad Request&nbsp;&nbsp;<a href="#rfc.xref.status.400.1">4.1</a>, <a href="#rfc.iref.s.22"><b>4.6.1</b></a>, <a href="#rfc.xref.status.400.2">10.2</a></li>
     5156                        <li>402 Payment Required&nbsp;&nbsp;<a href="#rfc.xref.status.402.1">4.1</a>, <a href="#rfc.iref.s.23"><b>4.6.2</b></a>, <a href="#rfc.xref.status.402.2">10.2</a></li>
     5157                        <li>403 Forbidden&nbsp;&nbsp;<a href="#rfc.xref.status.403.1">4.1</a>, <a href="#rfc.iref.s.24"><b>4.6.3</b></a>, <a href="#rfc.xref.status.403.2">10.2</a></li>
     5158                        <li>404 Not Found&nbsp;&nbsp;<a href="#rfc.xref.status.404.1">4.1</a>, <a href="#rfc.iref.s.25"><b>4.6.4</b></a>, <a href="#rfc.xref.status.404.2">10.2</a></li>
     5159                        <li>405 Method Not Allowed&nbsp;&nbsp;<a href="#rfc.xref.status.405.1">4.1</a>, <a href="#rfc.iref.s.26"><b>4.6.5</b></a>, <a href="#rfc.xref.status.405.2">10.2</a></li>
     5160                        <li>406 Not Acceptable&nbsp;&nbsp;<a href="#rfc.xref.status.406.1">4.1</a>, <a href="#rfc.iref.s.27"><b>4.6.6</b></a>, <a href="#rfc.xref.status.406.2">10.2</a></li>
     5161                        <li>408 Request Timeout&nbsp;&nbsp;<a href="#rfc.xref.status.408.1">4.1</a>, <a href="#rfc.iref.s.28"><b>4.6.7</b></a>, <a href="#rfc.xref.status.408.2">10.2</a></li>
     5162                        <li>409 Conflict&nbsp;&nbsp;<a href="#rfc.xref.status.409.1">4.1</a>, <a href="#rfc.iref.s.29"><b>4.6.8</b></a>, <a href="#rfc.xref.status.409.2">10.2</a></li>
     5163                        <li>410 Gone&nbsp;&nbsp;<a href="#rfc.xref.status.410.1">4.1</a>, <a href="#rfc.iref.s.30"><b>4.6.9</b></a>, <a href="#rfc.xref.status.410.2">10.2</a></li>
     5164                        <li>411 Length Required&nbsp;&nbsp;<a href="#rfc.xref.status.411.1">4.1</a>, <a href="#rfc.iref.s.31"><b>4.6.10</b></a>, <a href="#rfc.xref.status.411.2">10.2</a></li>
     5165                        <li>413 Request Representation Too Large&nbsp;&nbsp;<a href="#rfc.xref.status.413.1">4.1</a>, <a href="#rfc.iref.s.32"><b>4.6.11</b></a>, <a href="#rfc.xref.status.413.2">10.2</a></li>
     5166                        <li>414 URI Too Long&nbsp;&nbsp;<a href="#rfc.xref.status.414.1">4.1</a>, <a href="#rfc.iref.s.33"><b>4.6.12</b></a>, <a href="#rfc.xref.status.414.2">10.2</a></li>
     5167                        <li>415 Unsupported Media Type&nbsp;&nbsp;<a href="#rfc.xref.status.415.1">4.1</a>, <a href="#rfc.iref.s.34"><b>4.6.13</b></a>, <a href="#rfc.xref.status.415.2">10.2</a></li>
     5168                        <li>417 Expectation Failed&nbsp;&nbsp;<a href="#rfc.xref.status.417.1">4.1</a>, <a href="#rfc.iref.s.35"><b>4.6.14</b></a>, <a href="#rfc.xref.status.417.2">10.2</a></li>
     5169                        <li>426 Upgrade Required&nbsp;&nbsp;<a href="#rfc.xref.status.426.1">4.1</a>, <a href="#rfc.iref.s.36"><b>4.6.15</b></a>, <a href="#rfc.xref.status.426.2">10.2</a>, <a href="#rfc.xref.status.426.3">C</a></li>
     5170                        <li>500 Internal Server Error&nbsp;&nbsp;<a href="#rfc.xref.status.500.1">4.1</a>, <a href="#rfc.iref.s.38"><b>4.7.1</b></a>, <a href="#rfc.xref.status.500.2">10.2</a></li>
     5171                        <li>501 Not Implemented&nbsp;&nbsp;<a href="#rfc.xref.status.501.1">4.1</a>, <a href="#rfc.iref.s.39"><b>4.7.2</b></a>, <a href="#rfc.xref.status.501.2">10.2</a></li>
     5172                        <li>502 Bad Gateway&nbsp;&nbsp;<a href="#rfc.xref.status.502.1">4.1</a>, <a href="#rfc.iref.s.40"><b>4.7.3</b></a>, <a href="#rfc.xref.status.502.2">10.2</a></li>
     5173                        <li>503 Service Unavailable&nbsp;&nbsp;<a href="#rfc.xref.status.503.1">4.1</a>, <a href="#rfc.iref.s.41"><b>4.7.4</b></a>, <a href="#rfc.xref.status.503.2">10.2</a></li>
     5174                        <li>504 Gateway Timeout&nbsp;&nbsp;<a href="#rfc.xref.status.504.1">4.1</a>, <a href="#rfc.iref.s.42"><b>4.7.5</b></a>, <a href="#rfc.xref.status.504.2">10.2</a></li>
     5175                        <li>505 HTTP Version Not Supported&nbsp;&nbsp;<a href="#rfc.xref.status.505.1">4.1</a>, <a href="#rfc.iref.s.43"><b>4.7.6</b></a>, <a href="#rfc.xref.status.505.2">10.2</a></li>
     5176                     </ul>
     5177                  </li>
     5178                  <li>Status Codes Classes&nbsp;&nbsp;
     5179                     <ul>
     5180                        <li>1xx Informational&nbsp;&nbsp;<a href="#rfc.iref.s.3"><b>4.3</b></a></li>
     5181                        <li>2xx Successful&nbsp;&nbsp;<a href="#rfc.iref.s.6"><b>4.4</b></a></li>
     5182                        <li>3xx Redirection&nbsp;&nbsp;<a href="#rfc.iref.s.13"><b>4.5</b></a>, <a href="#rfc.xref.status.3xx.1">C</a></li>
     5183                        <li>4xx Client Error&nbsp;&nbsp;<a href="#rfc.iref.s.21"><b>4.6</b></a></li>
     5184                        <li>5xx Server Error&nbsp;&nbsp;<a href="#rfc.iref.s.37"><b>4.7</b></a></li>
    51585185                     </ul>
    51595186                  </li>
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1726 r1727  
    898898</artwork></figure>
    899899<t>
    900    Any successful (2xx) response to a CONNECT request indicates that the
     900   Any <x:ref>2xx (Successful)</x:ref> response to a CONNECT request indicates that the
    901901   proxy has established a connection to the requested host and port,
    902902   and has switched to tunneling the current connection to that server
     
    940940   origin server through another proxy.  In this case, the first proxy
    941941   &SHOULD; make a CONNECT request of that next proxy, requesting a tunnel
    942    to the authority.  A proxy &MUST-NOT; respond with any 2xx status code
     942   to the authority.  A proxy &MUST-NOT; respond with any <x:ref>2xx</x:ref> status code
    943943   unless it has either a direct or tunnel connection established to the
    944944   authority.
     
    953953<t>
    954954   An origin server which receives a CONNECT request for itself &MAY;
    955    respond with a 2xx status code to indicate that a connection is
     955   respond with a <x:ref>2xx</x:ref> status code to indicate that a connection is
    956956   established.  However, most origin servers do not implement CONNECT.
    957957</t>
     
    11381138  <list style="symbols">
    11391139    <t>
    1140       1xx: Informational - Request received, continuing process
    1141     </t>
    1142     <t>
    1143       2xx: Success - The action was successfully received,
     1140      <x:ref>1xx (Informational)</x:ref>: Request received, continuing process
     1141    </t>
     1142    <t>
     1143      <x:ref>2xx (Successful)</x:ref>: The action was successfully received,
    11441144        understood, and accepted
    11451145    </t>
    11461146    <t>
    1147       3xx: Redirection - Further action needs to be taken in order to
     1147      <x:ref>3xx (Redirection)</x:ref>: Further action needs to be taken in order to
    11481148        complete the request
    11491149    </t>
    11501150    <t>
    1151       4xx: Client Error - The request contains bad syntax or cannot
     1151      <x:ref>4xx (Client Error)</x:ref>: The request contains bad syntax or cannot
    11521152        be fulfilled
    11531153    </t>
    11541154    <t>
    1155       5xx: Server Error - The server failed to fulfill an apparently
     1155      <x:ref>5xx (Server Error)</x:ref>: The server failed to fulfill an apparently
    11561156        valid request
    11571157    </t>
     
    12811281
    12821282<section title="Informational 1xx" anchor="status.1xx">
     1283  <x:anchor-alias value="1xx"/>
     1284  <x:anchor-alias value="1xx (Informational)"/>
     1285  <iref primary="true" item="1xx Informational (status code class)" x:for-anchor=""/>
     1286  <iref primary="true" item="Status Codes Classes" subitem="1xx Informational" x:for-anchor=""/>
    12831287<t>
    12841288   This class of status code indicates a provisional response,
     
    13431347
    13441348<section title="Successful 2xx" anchor="status.2xx">
     1349  <x:anchor-alias value="2xx"/>
     1350  <x:anchor-alias value="2xx (Successful)"/>
     1351  <iref primary="true" item="2xx Successful (status code class)" x:for-anchor=""/>
     1352  <iref primary="true" item="Status Codes Classes" subitem="2xx Successful" x:for-anchor=""/>
    13451353<t>
    13461354   This class of status code indicates that the client's request was
     
    15081516
    15091517<section title="Redirection 3xx" anchor="status.3xx">
     1518  <x:anchor-alias value="3xx"/>
     1519  <x:anchor-alias value="3xx (Redirection)"/>
     1520  <iref primary="true" item="3xx Redirection (status code class)" x:for-anchor=""/>
     1521  <iref primary="true" item="Status Codes Classes" subitem="3xx Redirection" x:for-anchor=""/>
    15101522<t>
    15111523   This class of status code indicates that further action needs to be
     
    17671779
    17681780<section title="Client Error 4xx" anchor="status.4xx">
     1781  <x:anchor-alias value="4xx"/>
     1782  <x:anchor-alias value="4xx (Client Error)"/>
     1783  <iref primary="true" item="4xx Client Error (status code class)" x:for-anchor=""/>
     1784  <iref primary="true" item="Status Codes Classes" subitem="4xx Client Error" x:for-anchor=""/>
    17691785<t>
    17701786   The 4xx class of status code is intended for cases in which the
     
    20362052
    20372053<section title="Server Error 5xx" anchor="status.5xx">
     2054  <x:anchor-alias value="5xx"/>
     2055  <x:anchor-alias value="5xx (Server Error)"/>
     2056  <iref primary="true" item="5xx Server Error (status code class)" x:for-anchor=""/>
     2057  <iref primary="true" item="Status Codes Classes" subitem="5xx Server Error" x:for-anchor=""/>
    20382058<t>
    20392059   Response status codes beginning with the digit "5" indicate cases in
     
    36083628   the recipient &MUST; respond with a <x:ref>417 (Expectation Failed)</x:ref> status code. A
    36093629   recipient of a syntactically invalid Expectation header field &MUST; respond
    3610    with a 4xx status code other than 417.
     3630   with a <x:ref>4xx</x:ref> status code other than 417.
    36113631</t>
    36123632<t>
     
    36983718<t>
    36993719   For <x:ref>201 (Created)</x:ref> responses, the Location is the URI of the
    3700    new resource which was created by the request. For 3xx responses, the
     3720   new resource which was created by the request. For <x:ref>3xx</x:ref> responses, the
    37013721   location &SHOULD; indicate the server's preferred URI for automatic
    37023722   redirection to the resource.
     
    38293849   Unavailable)</x:ref> response to indicate how long the service is expected to
    38303850   be unavailable to the requesting client. This field &MAY; also be used
    3831    with any 3xx (Redirection) response to indicate the minimum time the
     3851   with any <x:ref>3xx (Redirection)</x:ref> response to indicate the minimum time the
    38323852   user-agent is asked to wait before issuing the redirected request.
    38333853</t>
     
    62436263    <t>
    62446264      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/10"/>:
    6245       "Safe Methods vs Redirection" (we missed the introduction to the 3xx
     6265      "Safe Methods vs Redirection" (we missed the introduction to the <x:ref>3xx</x:ref>
    62466266      status codes when fixing this previously)
    62476267    </t>
  • draft-ietf-httpbis/latest/p4-conditional.html

    r1725 r1727  
    992992         they <em class="bcp14">MUST</em> forward the request towards the origin server.
    993993      </p>
    994       <p id="rfc.section.3.1.p.6">If the request would, without the If-Match header field, result in anything other than a 2xx or 412 status code, then the
    995          If-Match header field <em class="bcp14">MUST</em> be ignored.
     994      <p id="rfc.section.3.1.p.6">If the request would, without the If-Match header field, result in anything other than a <a href="p2-semantics.html#status.2xx" class="smpl">2xx</a> or 412 status code, then the If-Match header field <em class="bcp14">MUST</em> be ignored.
    996995      </p>
    997996      <p id="rfc.section.3.1.p.7">Examples:</p>
     
    10231022      <p id="rfc.section.3.2.p.5">If none of the entity-tags match, then the server <em class="bcp14">MAY</em> perform the requested method as if the If-None-Match header field did not exist, but <em class="bcp14">MUST</em> also ignore any If-Modified-Since header field(s) in the request. That is, if no entity-tags match, then the server <em class="bcp14">MUST NOT</em> return a <a href="#status.304" class="smpl">304 (Not Modified)</a> response.
    10241023      </p>
    1025       <p id="rfc.section.3.2.p.6">If the request would, without the If-None-Match header field, result in anything other than a 2xx or 304 status code, then
    1026          the If-None-Match header field <em class="bcp14">MUST</em> be ignored. (See <a href="#rules.for.when.to.use.entity.tags.and.last-modified.dates" title="Rules for When to Use Entity-tags and Last-Modified Dates">Section&nbsp;2.4</a> for a discussion of server behavior when both If-Modified-Since and If-None-Match appear in the same request.)
     1024      <p id="rfc.section.3.2.p.6">If the request would, without the If-None-Match header field, result in anything other than a <a href="p2-semantics.html#status.2xx" class="smpl">2xx</a> or 304 status code, then the If-None-Match header field <em class="bcp14">MUST</em> be ignored. (See <a href="#rules.for.when.to.use.entity.tags.and.last-modified.dates" title="Rules for When to Use Entity-tags and Last-Modified Dates">Section&nbsp;2.4</a> for a discussion of server behavior when both If-Modified-Since and If-None-Match appear in the same request.)
    10271025      </p>
    10281026      <p id="rfc.section.3.2.p.7">Examples:</p>
     
    10901088</pre><p id="rfc.section.3.4.p.3">An example of the field is:</p>
    10911089      <div id="rfc.figure.u.16"></div><pre class="text">  If-Unmodified-Since: Sat, 29 Oct 1994 19:43:31 GMT
    1092 </pre><p id="rfc.section.3.4.p.5">If a request normally (i.e., in absence of the If-Unmodified-Since header field) would result in anything other than a 2xx
    1093          or 412 status code, the If-Unmodified-Since header field <em class="bcp14">SHOULD</em> be ignored.
     1090</pre><p id="rfc.section.3.4.p.5">If a request normally (i.e., in absence of the If-Unmodified-Since header field) would result in anything other than a <a href="p2-semantics.html#status.2xx" class="smpl">2xx</a> or 412 status code, the If-Unmodified-Since header field <em class="bcp14">SHOULD</em> be ignored.
    10941091      </p>
    10951092      <p id="rfc.section.3.4.p.6">If the specified date is invalid, the header field <em class="bcp14">MUST</em> be ignored.
  • draft-ietf-httpbis/latest/p4-conditional.xml

    r1726 r1727  
    768768<t>
    769769   If the request would, without the If-Match header field, result in
    770    anything other than a 2xx or 412 status code, then the If-Match header field
     770   anything other than a <x:ref>2xx</x:ref> or 412 status code, then the If-Match header field
    771771   &MUST; be ignored.
    772772</t>
     
    833833<t>
    834834   If the request would, without the If-None-Match header field, result
    835    in anything other than a 2xx or 304 status code, then the If-None-Match
     835   in anything other than a <x:ref>2xx</x:ref> or 304 status code, then the If-None-Match
    836836   header field &MUST; be ignored. (See <xref
    837837   target="rules.for.when.to.use.entity.tags.and.last-modified.dates"/> for
     
    964964<t>
    965965   If a request normally (i.e., in absence of the If-Unmodified-Since
    966    header field) would result in anything other than a 2xx or 412 status code,
     966   header field) would result in anything other than a <x:ref>2xx</x:ref> or 412 status code,
    967967   the If-Unmodified-Since header field &SHOULD; be ignored.
    968968</t>
     
    11941194  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p2-semantics-&ID-VERSION;"/>
    11951195  <x:source href="p2-semantics.xml" basename="p2-semantics">
     1196    <x:defines>2xx</x:defines>
    11961197    <x:defines>200 (OK)</x:defines>
    11971198  </x:source>
  • draft-ietf-httpbis/latest/p6-cache.html

    r1725 r1727  
    11491149      <p id="rfc.section.2.6.p.4">A cache <em class="bcp14">MUST</em> invalidate the effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) when it receives a non-error response to a request with a method whose safety is unknown.
    11501150      </p>
    1151       <p id="rfc.section.2.6.p.5">Here, a "non-error response" is one with a 2xx or 3xx status code. "Invalidate" means that the cache will either remove all
    1152          stored responses related to the effective request URI, or will mark these as "invalid" and in need of a mandatory validation
    1153          before they can be returned in response to a subsequent request.
     1151      <p id="rfc.section.2.6.p.5">Here, a "non-error response" is one with a <a href="p2-semantics.html#status.2xx" class="smpl">2xx</a> or <a href="p2-semantics.html#status.3xx" class="smpl">3xx</a> status code. "Invalidate" means that the cache will either remove all stored responses related to the effective request URI,
     1152         or will mark these as "invalid" and in need of a mandatory validation before they can be returned in response to a subsequent
     1153         request.
    11541154      </p>
    11551155      <p id="rfc.section.2.6.p.6">Note that this does not guarantee that all appropriate responses are invalidated. For example, the request that caused the
  • draft-ietf-httpbis/latest/p6-cache.xml

    r1726 r1727  
    10271027</t>
    10281028<t>
    1029    Here, a "non-error response" is one with a 2xx or 3xx status code.
     1029   Here, a "non-error response" is one with a <x:ref>2xx</x:ref> or <x:ref>3xx</x:ref> status code.
    10301030   "Invalidate" means that the cache will either remove all stored
    10311031   responses related to the effective request URI, or will mark these as
     
    22882288    <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p2-semantics-&ID-VERSION;" />
    22892289    <x:source basename="p2-semantics" href="p2-semantics.xml">
     2290      <x:defines>2xx</x:defines>
    22902291      <x:defines>200 (OK)</x:defines>
     2292      <x:defines>3xx</x:defines>
    22912293      <x:defines>404 (Not Found)</x:defines>
    22922294      <x:defines>504 (Gateway Timeout)</x:defines>
Note: See TracChangeset for help on using the changeset viewer.