Changeset 1898


Ignore:
Timestamp:
Sep 15, 2012, 3:28:59 AM (7 years ago)
Author:
julian.reschke@…
Message:

Trim index.

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

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/extract-method-defs.xslt

    r1728 r1898  
    1515      <ttcol>Idempotent</ttcol>
    1616      <ttcol>Reference</ttcol>
    17       <xsl:apply-templates select="//section[iref/@item='Methods']">
    18         <xsl:sort select="iref[@item='Methods']/@subitem"/>
     17      <xsl:apply-templates select="//section[iref[contains(@item,' method') and @primary='true']]">
     18        <xsl:sort select="iref[contains(@item,' method') and @primary='true']/@item"/>
    1919      </xsl:apply-templates>
    2020    </texttable>
     
    7575
    7676<xsl:template match="section">
    77 
    78   <xsl:variable name="text" select="iref[@item='Methods']/@subitem"/>
     77  <xsl:variable name="t" select="iref[contains(@item,' method')]/@item"/>
     78  <xsl:variable name="text" select="substring-before($t,' method')"/>
    7979
    8080  <xsl:variable name="safe" xmlns:p2="urn:ietf:id:draft-ietf-httpbis-p2-semantics#">
  • draft-ietf-httpbis/latest/p2-semantics.html

    r1895 r1898  
    13671367      <h3 id="rfc.section.5.3.1"><a href="#rfc.section.5.3.1">5.3.1</a>&nbsp;<a id="GET" href="#GET">GET</a></h3>
    13681368      <div id="rfc.iref.g.6"></div>
    1369       <div id="rfc.iref.m.1"></div>
    13701369      <p id="rfc.section.5.3.1.p.1">The GET method requests transfer of a current representation of the target resource.</p>
    13711370      <p id="rfc.section.5.3.1.p.2">If the target resource is a data-producing process, it is the produced data which shall be returned as the representation
     
    13881387      <h3 id="rfc.section.5.3.2"><a href="#rfc.section.5.3.2">5.3.2</a>&nbsp;<a id="HEAD" href="#HEAD">HEAD</a></h3>
    13891388      <div id="rfc.iref.h.1"></div>
    1390       <div id="rfc.iref.m.2"></div>
    13911389      <p id="rfc.section.5.3.2.p.1">The HEAD method is identical to GET except that the server <em class="bcp14">MUST NOT</em> return a message body in the response. The metadata contained in the HTTP header fields in response to a HEAD request <em class="bcp14">SHOULD</em> be identical to the information sent in response to a GET request. This method can be used for obtaining metadata about the
    13921390         representation implied by the request without transferring the representation body. This method is often used for testing
     
    13991397      </p>
    14001398      <div id="rfc.iref.p.2"></div>
    1401       <div id="rfc.iref.m.3"></div>
    14021399      <h3 id="rfc.section.5.3.3"><a href="#rfc.section.5.3.3">5.3.3</a>&nbsp;<a id="POST" href="#POST">POST</a></h3>
    14031400      <p id="rfc.section.5.3.3.p.1">The POST method requests that the origin server accept the representation enclosed in the request as data to be processed
     
    14241421      <h3 id="rfc.section.5.3.4"><a href="#rfc.section.5.3.4">5.3.4</a>&nbsp;<a id="PUT" href="#PUT">PUT</a></h3>
    14251422      <div id="rfc.iref.p.3"></div>
    1426       <div id="rfc.iref.m.4"></div>
    14271423      <p id="rfc.section.5.3.4.p.1">The PUT method requests that the state of the target resource be created or replaced with the state defined by the representation
    14281424         enclosed in the request message payload. A successful PUT of a given representation would suggest that a subsequent GET on
     
    14881484      <h3 id="rfc.section.5.3.5"><a href="#rfc.section.5.3.5">5.3.5</a>&nbsp;<a id="DELETE" href="#DELETE">DELETE</a></h3>
    14891485      <div id="rfc.iref.d.1"></div>
    1490       <div id="rfc.iref.m.5"></div>
    14911486      <p id="rfc.section.5.3.5.p.1">The DELETE method requests that the origin server delete the target resource. This method <em class="bcp14">MAY</em> be overridden by human intervention (or other means) on the origin server. The client cannot be guaranteed that the operation
    14921487         has been carried out, even if the status code returned from the origin server indicates that the action has been completed
     
    15031498      </p>
    15041499      <div id="rfc.iref.c.7"></div>
    1505       <div id="rfc.iref.m.6"></div>
    15061500      <h3 id="rfc.section.5.3.6"><a href="#rfc.section.5.3.6">5.3.6</a>&nbsp;<a id="CONNECT" href="#CONNECT">CONNECT</a></h3>
    15071501      <p id="rfc.section.5.3.6.p.1">The CONNECT method requests that the proxy establish a tunnel to the request-target and, if successful, thereafter restrict
     
    15451539      <h3 id="rfc.section.5.3.7"><a href="#rfc.section.5.3.7">5.3.7</a>&nbsp;<a id="OPTIONS" href="#OPTIONS">OPTIONS</a></h3>
    15461540      <div id="rfc.iref.o.1"></div>
    1547       <div id="rfc.iref.m.7"></div>
    15481541      <p id="rfc.section.5.3.7.p.1">The OPTIONS method requests information about the communication options available on the request/response chain identified
    15491542         by the effective request URI. This method allows a client to determine the options and/or requirements associated with a resource,
     
    15691562      <h3 id="rfc.section.5.3.8"><a href="#rfc.section.5.3.8">5.3.8</a>&nbsp;<a id="TRACE" href="#TRACE">TRACE</a></h3>
    15701563      <div id="rfc.iref.t.1"></div>
    1571       <div id="rfc.iref.m.8"></div>
    15721564      <p id="rfc.section.5.3.8.p.1">The TRACE method requests a remote, application-level loop-back of the request message. The final recipient of the request <em class="bcp14">SHOULD</em> reflect the message received back to the client as the message body of a <a href="#status.200" class="smpl">200 (OK)</a> response. The final recipient is either the origin server or the first proxy to receive a <a href="#header.max-forwards" class="smpl">Max-Forwards</a> value of zero (0) in the request (see <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.2" title="Max-Forwards">Section&nbsp;6.1.1</a>). A TRACE request <em class="bcp14">MUST NOT</em> include a message body.
    15731565      </p>
     
    16141606         </table>
    16151607      </div>
    1616       <div id="rfc.iref.m.9"></div>
     1608      <div id="rfc.iref.m.1"></div>
    16171609      <h3 id="rfc.section.6.1.1"><a href="#rfc.section.6.1.1">6.1.1</a>&nbsp;<a id="header.max-forwards" href="#header.max-forwards">Max-Forwards</a></h3>
    16181610      <p id="rfc.section.6.1.1.p.1">The "Max-Forwards" header field provides a mechanism with the TRACE (<a href="#TRACE" id="rfc.xref.TRACE.2" title="TRACE">Section&nbsp;5.3.8</a>) and OPTIONS (<a href="#OPTIONS" id="rfc.xref.OPTIONS.2" title="OPTIONS">Section&nbsp;5.3.7</a>) methods to limit the number of times that the request is forwarded by proxies. This can be useful when the client is attempting
     
    16401632      </p>
    16411633      <p id="rfc.section.6.1.2.p.4">The only expectation defined by this specification is:</p>
    1642       <p id="rfc.section.6.1.2.p.5"><span id="rfc.iref.40"></span><span id="rfc.iref.e.2"></span> 100-continue
     1634      <p id="rfc.section.6.1.2.p.5"><span id="rfc.iref.32"></span><span id="rfc.iref.e.2"></span> 100-continue
    16431635      </p>
    16441636      <ul class="empty">
     
    23262318      <p id="rfc.section.7.1.p.2">Note that this list is not exhaustive — it does not include extension status codes defined in other specifications.</p>
    23272319      <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a>&nbsp;<a id="status.1xx" href="#status.1xx">Informational 1xx</a></h2>
    2328       <div id="rfc.iref.62"></div>
     2320      <div id="rfc.iref.54"></div>
    23292321      <div id="rfc.iref.s.3"></div>
    23302322      <p id="rfc.section.7.2.p.1">This class of status code indicates a provisional response, consisting only of the status-line and optional header fields,
     
    23392331         a request, then it need not forward the corresponding <a href="#status.100" class="smpl">100 (Continue)</a> response(s).)
    23402332      </p>
    2341       <div id="rfc.iref.63"></div>
     2333      <div id="rfc.iref.55"></div>
    23422334      <h3 id="rfc.section.7.2.1"><a href="#rfc.section.7.2.1">7.2.1</a>&nbsp;<a id="status.100" href="#status.100">100 Continue</a></h3>
    23432335      <p id="rfc.section.7.2.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
     
    23452337         server <em class="bcp14">MUST</em> send a final response after the request has been completed. See <a href="#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section&nbsp;6.1.2.1</a> for detailed discussion of the use and handling of this status code.
    23462338      </p>
    2347       <div id="rfc.iref.63"></div>
     2339      <div id="rfc.iref.55"></div>
    23482340      <h3 id="rfc.section.7.2.2"><a href="#rfc.section.7.2.2">7.2.2</a>&nbsp;<a id="status.101" href="#status.101">101 Switching Protocols</a></h3>
    23492341      <p id="rfc.section.7.2.2.p.1">The server understands and is willing to comply with the client's request, via the <a href="p1-messaging.html#header.upgrade" class="smpl">Upgrade</a> message header field (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 6.3</a> of <a href="#Part1" id="rfc.xref.Part1.19"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>), for a change in the application protocol being used on this connection. The server will switch protocols to those defined
     
    23552347      </p>
    23562348      <h2 id="rfc.section.7.3"><a href="#rfc.section.7.3">7.3</a>&nbsp;<a id="status.2xx" href="#status.2xx">Successful 2xx</a></h2>
    2357       <div id="rfc.iref.63"></div>
     2349      <div id="rfc.iref.55"></div>
    23582350      <div id="rfc.iref.s.4"></div>
    23592351      <p id="rfc.section.7.3.p.1">This class of status code indicates that the client's request was successfully received, understood, and accepted.</p>
    2360       <div id="rfc.iref.64"></div>
     2352      <div id="rfc.iref.56"></div>
    23612353      <h3 id="rfc.section.7.3.1"><a href="#rfc.section.7.3.1">7.3.1</a>&nbsp;<a id="status.200" href="#status.200">200 OK</a></h3>
    23622354      <p id="rfc.section.7.3.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>
     
    23732365      <p id="rfc.section.7.3.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 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to determine freshness for 200 responses.
    23742366      </p>
    2375       <div id="rfc.iref.64"></div>
     2367      <div id="rfc.iref.56"></div>
    23762368      <h3 id="rfc.section.7.3.2"><a href="#rfc.section.7.3.2">7.3.2</a>&nbsp;<a id="status.201" href="#status.201">201 Created</a></h3>
    23772369      <p id="rfc.section.7.3.2.p.1">The request has been fulfilled and has resulted in one or more new resources being created.</p>
     
    23852377         the <a href="#header.location" class="smpl">Location</a> 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.12"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>).
    23862378      </p>
    2387       <div id="rfc.iref.64"></div>
     2379      <div id="rfc.iref.56"></div>
    23882380      <h3 id="rfc.section.7.3.3"><a href="#rfc.section.7.3.3">7.3.3</a>&nbsp;<a id="status.202" href="#status.202">202 Accepted</a></h3>
    23892381      <p id="rfc.section.7.3.3.p.1">The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually
     
    23962388         user can expect the request to be fulfilled.
    23972389      </p>
    2398       <div id="rfc.iref.64"></div>
     2390      <div id="rfc.iref.56"></div>
    23992391      <h3 id="rfc.section.7.3.4"><a href="#rfc.section.7.3.4">7.3.4</a>&nbsp;<a id="status.203" href="#status.203">203 Non-Authoritative Information</a></h3>
    24002392      <p id="rfc.section.7.3.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.20"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[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 7.2</a> of <a href="#Part6" id="rfc.xref.Part6.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
     
    24052397      <p id="rfc.section.7.3.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 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.11"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to determine freshness for 203 responses.
    24062398      </p>
    2407       <div id="rfc.iref.64"></div>
     2399      <div id="rfc.iref.56"></div>
    24082400      <h3 id="rfc.section.7.3.5"><a href="#rfc.section.7.3.5">7.3.5</a>&nbsp;<a id="status.204" href="#status.204">204 No Content</a></h3>
    24092401      <p id="rfc.section.7.3.5.p.1">The 204 (No Content) status code indicates that the server has successfully fulfilled the request and that there is no additional
     
    24252417      <p id="rfc.section.7.3.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.
    24262418      </p>
    2427       <div id="rfc.iref.64"></div>
     2419      <div id="rfc.iref.56"></div>
    24282420      <h3 id="rfc.section.7.3.6"><a href="#rfc.section.7.3.6">7.3.6</a>&nbsp;<a id="status.205" href="#status.205">205 Reset Content</a></h3>
    24292421      <p id="rfc.section.7.3.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
     
    24342426      </p>
    24352427      <h2 id="rfc.section.7.4"><a href="#rfc.section.7.4">7.4</a>&nbsp;<a id="status.3xx" href="#status.3xx">Redirection 3xx</a></h2>
    2436       <div id="rfc.iref.64"></div>
     2428      <div id="rfc.iref.56"></div>
    24372429      <div id="rfc.iref.s.5"></div>
    24382430      <p id="rfc.section.7.4.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.
     
    24802472         </p>
    24812473      </div>
    2482       <div id="rfc.iref.65"></div>
     2474      <div id="rfc.iref.57"></div>
    24832475      <h3 id="rfc.section.7.4.1"><a href="#rfc.section.7.4.1">7.4.1</a>&nbsp;<a id="status.300" href="#status.300">300 Multiple Choices</a></h3>
    24842476      <p id="rfc.section.7.4.1.p.1">The target resource has more than one representation, each with its own specific location, and reactive negotiation information
     
    24942486      <p id="rfc.section.7.4.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 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.12"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to determine freshness for 300 responses.
    24952487      </p>
    2496       <div id="rfc.iref.65"></div>
     2488      <div id="rfc.iref.57"></div>
    24972489      <h3 id="rfc.section.7.4.2"><a href="#rfc.section.7.4.2">7.4.2</a>&nbsp;<a id="status.301" href="#status.301">301 Moved Permanently</a></h3>
    24982490      <p id="rfc.section.7.4.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
     
    25072499         </p>
    25082500      </div>
    2509       <div id="rfc.iref.65"></div>
     2501      <div id="rfc.iref.57"></div>
    25102502      <h3 id="rfc.section.7.4.3"><a href="#rfc.section.7.4.3">7.4.3</a>&nbsp;<a id="status.302" href="#status.302">302 Found</a></h3>
    25112503      <p id="rfc.section.7.4.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.
     
    25172509         </p>
    25182510      </div>
    2519       <div id="rfc.iref.65"></div>
     2511      <div id="rfc.iref.57"></div>
    25202512      <h3 id="rfc.section.7.4.4"><a href="#rfc.section.7.4.4">7.4.4</a>&nbsp;<a id="status.303" href="#status.303">303 See Other</a></h3>
    25212513      <p id="rfc.section.7.4.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
     
    25372529      <p id="rfc.section.7.4.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 <a href="#header.location" class="smpl">Location</a> URI.
    25382530      </p>
    2539       <div id="rfc.iref.65"></div>
     2531      <div id="rfc.iref.57"></div>
    25402532      <h3 id="rfc.section.7.4.5"><a href="#rfc.section.7.4.5">7.4.5</a>&nbsp;<a id="status.305" href="#status.305">305 Use Proxy</a></h3>
    25412533      <p id="rfc.section.7.4.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.
    25422534      </p>
    2543       <div id="rfc.iref.65"></div>
     2535      <div id="rfc.iref.57"></div>
    25442536      <h3 id="rfc.section.7.4.6"><a href="#rfc.section.7.4.6">7.4.6</a>&nbsp;<a id="status.306" href="#status.306">306 (Unused)</a></h3>
    25452537      <p id="rfc.section.7.4.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>
    2546       <div id="rfc.iref.65"></div>
     2538      <div id="rfc.iref.57"></div>
    25472539      <h3 id="rfc.section.7.4.7"><a href="#rfc.section.7.4.7">7.4.7</a>&nbsp;<a id="status.307" href="#status.307">307 Temporary Redirect</a></h3>
    25482540      <p id="rfc.section.7.4.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.
     
    25572549      </div>
    25582550      <h2 id="rfc.section.7.5"><a href="#rfc.section.7.5">7.5</a>&nbsp;<a id="status.4xx" href="#status.4xx">Client Error 4xx</a></h2>
    2559       <div id="rfc.iref.65"></div>
     2551      <div id="rfc.iref.57"></div>
    25602552      <div id="rfc.iref.s.6"></div>
    25612553      <p id="rfc.section.7.5.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
     
    25632555         These status codes are applicable to any request method. User agents <em class="bcp14">SHOULD</em> display any included representation to the user.
    25642556      </p>
    2565       <div id="rfc.iref.66"></div>
     2557      <div id="rfc.iref.58"></div>
    25662558      <h3 id="rfc.section.7.5.1"><a href="#rfc.section.7.5.1">7.5.1</a>&nbsp;<a id="status.400" href="#status.400">400 Bad Request</a></h3>
    25672559      <p id="rfc.section.7.5.1.p.1">The server cannot or will not process the request, due to a client error (e.g., malformed syntax).</p>
    2568       <div id="rfc.iref.66"></div>
     2560      <div id="rfc.iref.58"></div>
    25692561      <h3 id="rfc.section.7.5.2"><a href="#rfc.section.7.5.2">7.5.2</a>&nbsp;<a id="status.402" href="#status.402">402 Payment Required</a></h3>
    25702562      <p id="rfc.section.7.5.2.p.1">This code is reserved for future use.</p>
    2571       <div id="rfc.iref.66"></div>
     2563      <div id="rfc.iref.58"></div>
    25722564      <h3 id="rfc.section.7.5.3"><a href="#rfc.section.7.5.3">7.5.3</a>&nbsp;<a id="status.403" href="#status.403">403 Forbidden</a></h3>
    25732565      <p id="rfc.section.7.5.3.p.1">The server understood the request, but refuses to authorize it. Providing different user authentication credentials might
     
    25782570            (Not Found)</a>  <em class="bcp14">MAY</em> be used instead.
    25792571      </p>
    2580       <div id="rfc.iref.66"></div>
     2572      <div id="rfc.iref.58"></div>
    25812573      <h3 id="rfc.section.7.5.4"><a href="#rfc.section.7.5.4">7.5.4</a>&nbsp;<a id="status.404" href="#status.404">404 Not Found</a></h3>
    25822574      <p id="rfc.section.7.5.4.p.1">The server has not found anything matching the effective request URI. No indication is given of whether the condition is temporary
     
    25852577         has been refused, or when no other response is applicable.
    25862578      </p>
    2587       <div id="rfc.iref.66"></div>
     2579      <div id="rfc.iref.58"></div>
    25882580      <h3 id="rfc.section.7.5.5"><a href="#rfc.section.7.5.5">7.5.5</a>&nbsp;<a id="status.405" href="#status.405">405 Method Not Allowed</a></h3>
    25892581      <p id="rfc.section.7.5.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 <a href="#header.allow" class="smpl">Allow</a> header field containing a list of valid methods for the requested resource.
    25902582      </p>
    2591       <div id="rfc.iref.66"></div>
     2583      <div id="rfc.iref.58"></div>
    25922584      <h3 id="rfc.section.7.5.6"><a href="#rfc.section.7.5.6">7.5.6</a>&nbsp;<a id="status.406" href="#status.406">406 Not Acceptable</a></h3>
    25932585      <p id="rfc.section.7.5.6.p.1">The resource identified by the request is only capable of generating response representations which have content characteristics
     
    26062598      <p id="rfc.section.7.5.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.
    26072599      </p>
    2608       <div id="rfc.iref.66"></div>
     2600      <div id="rfc.iref.58"></div>
    26092601      <h3 id="rfc.section.7.5.7"><a href="#rfc.section.7.5.7">7.5.7</a>&nbsp;<a id="status.408" href="#status.408">408 Request Timeout</a></h3>
    26102602      <p id="rfc.section.7.5.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.
    26112603      </p>
    2612       <div id="rfc.iref.66"></div>
     2604      <div id="rfc.iref.58"></div>
    26132605      <h3 id="rfc.section.7.5.8"><a href="#rfc.section.7.5.8">7.5.8</a>&nbsp;<a id="status.409" href="#status.409">409 Conflict</a></h3>
    26142606      <p id="rfc.section.7.5.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
     
    26222614         contain a list of the differences between the two versions.
    26232615      </p>
    2624       <div id="rfc.iref.66"></div>
     2616      <div id="rfc.iref.58"></div>
    26252617      <h3 id="rfc.section.7.5.9"><a href="#rfc.section.7.5.9">7.5.9</a>&nbsp;<a id="status.410" href="#status.410">410 Gone</a></h3>
    26262618      <p id="rfc.section.7.5.9.p.1">The target resource is no longer available at the server and no forwarding address is known. This condition is expected to
     
    26362628      <p id="rfc.section.7.5.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 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.14"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to determine freshness for 410 responses.
    26372629      </p>
    2638       <div id="rfc.iref.66"></div>
     2630      <div id="rfc.iref.58"></div>
    26392631      <h3 id="rfc.section.7.5.10"><a href="#rfc.section.7.5.10">7.5.10</a>&nbsp;<a id="status.411" href="#status.411">411 Length Required</a></h3>
    26402632      <p id="rfc.section.7.5.10.p.1">The server refuses to accept the request without a defined <a href="p1-messaging.html#header.content-length" class="smpl">Content-Length</a>. 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
    26412633         message.
    26422634      </p>
    2643       <div id="rfc.iref.66"></div>
     2635      <div id="rfc.iref.58"></div>
    26442636      <h3 id="rfc.section.7.5.11"><a href="#rfc.section.7.5.11">7.5.11</a>&nbsp;<a id="status.413" href="#status.413">413 Request Representation Too Large</a></h3>
    26452637      <p id="rfc.section.7.5.11.p.1">The server is refusing to process a request because the request representation is larger than the server is willing or able
     
    26482640      <p id="rfc.section.7.5.11.p.2">If the condition is temporary, the server <em class="bcp14">SHOULD</em> include a <a href="#header.retry-after" class="smpl">Retry-After</a> header field to indicate that it is temporary and after what time the client <em class="bcp14">MAY</em> try again.
    26492641      </p>
    2650       <div id="rfc.iref.66"></div>
     2642      <div id="rfc.iref.58"></div>
    26512643      <h3 id="rfc.section.7.5.12"><a href="#rfc.section.7.5.12">7.5.12</a>&nbsp;<a id="status.414" href="#status.414">414 URI Too Long</a></h3>
    26522644      <p id="rfc.section.7.5.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.
     
    26562648         in some servers using fixed-length buffers for reading or manipulating the request-target.
    26572649      </p>
    2658       <div id="rfc.iref.66"></div>
     2650      <div id="rfc.iref.58"></div>
    26592651      <h3 id="rfc.section.7.5.13"><a href="#rfc.section.7.5.13">7.5.13</a>&nbsp;<a id="status.415" href="#status.415">415 Unsupported Media Type</a></h3>
    26602652      <p id="rfc.section.7.5.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
    26612653         on the target resource.
    26622654      </p>
    2663       <div id="rfc.iref.66"></div>
     2655      <div id="rfc.iref.58"></div>
    26642656      <h3 id="rfc.section.7.5.14"><a href="#rfc.section.7.5.14">7.5.14</a>&nbsp;<a id="status.417" href="#status.417">417 Expectation Failed</a></h3>
    26652657      <p id="rfc.section.7.5.14.p.1">The expectation given in an <a href="#header.expect" class="smpl">Expect</a> header field (see <a href="#header.expect" id="rfc.xref.header.expect.2" title="Expect">Section&nbsp;6.1.2</a>) could not be met by this server, or, if the server is a proxy, the server has unambiguous evidence that the request could
    26662658         not be met by the next-hop server.
    26672659      </p>
    2668       <div id="rfc.iref.66"></div>
     2660      <div id="rfc.iref.58"></div>
    26692661      <h3 id="rfc.section.7.5.15"><a href="#rfc.section.7.5.15">7.5.15</a>&nbsp;<a id="status.426" href="#status.426">426 Upgrade Required</a></h3>
    26702662      <p id="rfc.section.7.5.15.p.1">The request can not be completed without a prior protocol upgrade. This response <em class="bcp14">MUST</em> include an <a href="p1-messaging.html#header.upgrade" class="smpl">Upgrade</a> header field (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 6.3</a> of <a href="#Part1" id="rfc.xref.Part1.22"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) specifying the required protocols.
     
    26822674      </p>
    26832675      <h2 id="rfc.section.7.6"><a href="#rfc.section.7.6">7.6</a>&nbsp;<a id="status.5xx" href="#status.5xx">Server Error 5xx</a></h2>
    2684       <div id="rfc.iref.66"></div>
     2676      <div id="rfc.iref.58"></div>
    26852677      <div id="rfc.iref.s.7"></div>
    26862678      <p id="rfc.section.7.6.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
     
    26882680         User agents <em class="bcp14">SHOULD</em> display any included representation to the user. These response codes are applicable to any request method.
    26892681      </p>
    2690       <div id="rfc.iref.67"></div>
     2682      <div id="rfc.iref.59"></div>
    26912683      <h3 id="rfc.section.7.6.1"><a href="#rfc.section.7.6.1">7.6.1</a>&nbsp;<a id="status.500" href="#status.500">500 Internal Server Error</a></h3>
    26922684      <p id="rfc.section.7.6.1.p.1">The server encountered an unexpected condition which prevented it from fulfilling the request.</p>
    2693       <div id="rfc.iref.67"></div>
     2685      <div id="rfc.iref.59"></div>
    26942686      <h3 id="rfc.section.7.6.2"><a href="#rfc.section.7.6.2">7.6.2</a>&nbsp;<a id="status.501" href="#status.501">501 Not Implemented</a></h3>
    26952687      <p id="rfc.section.7.6.2.p.1">The server does not support the functionality required to fulfill the request. This is the appropriate response when the server
    26962688         does not recognize the request method and is not capable of supporting it for any resource.
    26972689      </p>
    2698       <div id="rfc.iref.67"></div>
     2690      <div id="rfc.iref.59"></div>
    26992691      <h3 id="rfc.section.7.6.3"><a href="#rfc.section.7.6.3">7.6.3</a>&nbsp;<a id="status.502" href="#status.502">502 Bad Gateway</a></h3>
    27002692      <p id="rfc.section.7.6.3.p.1">The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting
    27012693         to fulfill the request.
    27022694      </p>
    2703       <div id="rfc.iref.67"></div>
     2695      <div id="rfc.iref.59"></div>
    27042696      <h3 id="rfc.section.7.6.4"><a href="#rfc.section.7.6.4">7.6.4</a>&nbsp;<a id="status.503" href="#status.503">503 Service Unavailable</a></h3>
    27052697      <p id="rfc.section.7.6.4.p.1">The server is currently unable to handle the request due to a temporary overloading or maintenance of the server.</p>
     
    27132705         </p>
    27142706      </div>
    2715       <div id="rfc.iref.67"></div>
     2707      <div id="rfc.iref.59"></div>
    27162708      <h3 id="rfc.section.7.6.5"><a href="#rfc.section.7.6.5">7.6.5</a>&nbsp;<a id="status.504" href="#status.504">504 Gateway Timeout</a></h3>
    27172709      <p id="rfc.section.7.6.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
     
    27232715         </p>
    27242716      </div>
    2725       <div id="rfc.iref.67"></div>
     2717      <div id="rfc.iref.59"></div>
    27262718      <h3 id="rfc.section.7.6.6"><a href="#rfc.section.7.6.6">7.6.6</a>&nbsp;<a id="status.505" href="#status.505">505 HTTP Version Not Supported</a></h3>
    27272719      <p id="rfc.section.7.6.6.p.1">The server does not support, or refuses to support, the protocol version that was used in the request message. The server
     
    41044096         to HTTP also need to be aware of the differences because some conversions might be required.
    41054097      </p>
    4106       <div id="rfc.iref.m.10"></div>
     4098      <div id="rfc.iref.m.2"></div>
    41074099      <h2 id="rfc.section.A.1"><a href="#rfc.section.A.1">A.1</a>&nbsp;<a id="mime-version" href="#mime-version">MIME-Version</a></h2>
    41084100      <p id="rfc.section.A.1.p.1">HTTP is not a MIME-compliant protocol. However, HTTP/1.1 messages <em class="bcp14">MAY</em> include a single MIME-Version header field to indicate what version of the MIME protocol was used to construct the message.
     
    49634955         <ul class="ind">
    49644956            <li><a id="rfc.index.1" href="#rfc.index.1"><b>1</b></a><ul>
    4965                   <li>100 Continue (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.100.1">6.1.2.1</a>, <a href="#rfc.xref.status.100.2">6.1.2.1</a>, <a href="#rfc.xref.status.100.3">7.1</a>, <a href="#rfc.iref.63"><b>7.2.1</b></a>, <a href="#rfc.xref.status.100.4">10.2.3</a></li>
    4966                   <li>100-continue (expect value)&nbsp;&nbsp;<a href="#rfc.iref.40"><b>6.1.2</b></a></li>
    4967                   <li>101 Switching Protocols (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.101.1">7.1</a>, <a href="#rfc.iref.63"><b>7.2.2</b></a>, <a href="#rfc.xref.status.101.2">10.2.3</a></li>
    4968                   <li>1xx Informational (status code class)&nbsp;&nbsp;<a href="#rfc.iref.62"><b>7.2</b></a></li>
     4957                  <li>100 Continue (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.100.1">6.1.2.1</a>, <a href="#rfc.xref.status.100.2">6.1.2.1</a>, <a href="#rfc.xref.status.100.3">7.1</a>, <a href="#rfc.iref.55"><b>7.2.1</b></a>, <a href="#rfc.xref.status.100.4">10.2.3</a></li>
     4958                  <li>100-continue (expect value)&nbsp;&nbsp;<a href="#rfc.iref.32"><b>6.1.2</b></a></li>
     4959                  <li>101 Switching Protocols (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.101.1">7.1</a>, <a href="#rfc.iref.55"><b>7.2.2</b></a>, <a href="#rfc.xref.status.101.2">10.2.3</a></li>
     4960                  <li>1xx Informational (status code class)&nbsp;&nbsp;<a href="#rfc.iref.54"><b>7.2</b></a></li>
    49694961               </ul>
    49704962            </li>
    49714963            <li><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul>
    4972                   <li>200 OK (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.200.1">7.1</a>, <a href="#rfc.iref.64"><b>7.3.1</b></a>, <a href="#rfc.xref.status.200.2">10.2.3</a></li>
    4973                   <li>201 Created (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.201.1">7.1</a>, <a href="#rfc.iref.64"><b>7.3.2</b></a>, <a href="#rfc.xref.status.201.2">10.2.3</a></li>
    4974                   <li>202 Accepted (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.202.1">7.1</a>, <a href="#rfc.iref.64"><b>7.3.3</b></a>, <a href="#rfc.xref.status.202.2">10.2.3</a></li>
    4975                   <li>203 Non-Authoritative Information (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.203.1">7.1</a>, <a href="#rfc.iref.64"><b>7.3.4</b></a>, <a href="#rfc.xref.status.203.2">10.2.3</a>, <a href="#rfc.xref.status.203.3">C</a></li>
    4976                   <li>204 No Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.204.1">7.1</a>, <a href="#rfc.iref.64"><b>7.3.5</b></a>, <a href="#rfc.xref.status.204.2">10.2.3</a></li>
    4977                   <li>205 Reset Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.205.1">7.1</a>, <a href="#rfc.iref.64"><b>7.3.6</b></a>, <a href="#rfc.xref.status.205.2">10.2.3</a></li>
    4978                   <li>2xx Successful (status code class)&nbsp;&nbsp;<a href="#rfc.iref.63"><b>7.3</b></a></li>
     4964                  <li>200 OK (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.200.1">7.1</a>, <a href="#rfc.iref.56"><b>7.3.1</b></a>, <a href="#rfc.xref.status.200.2">10.2.3</a></li>
     4965                  <li>201 Created (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.201.1">7.1</a>, <a href="#rfc.iref.56"><b>7.3.2</b></a>, <a href="#rfc.xref.status.201.2">10.2.3</a></li>
     4966                  <li>202 Accepted (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.202.1">7.1</a>, <a href="#rfc.iref.56"><b>7.3.3</b></a>, <a href="#rfc.xref.status.202.2">10.2.3</a></li>
     4967                  <li>203 Non-Authoritative Information (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.203.1">7.1</a>, <a href="#rfc.iref.56"><b>7.3.4</b></a>, <a href="#rfc.xref.status.203.2">10.2.3</a>, <a href="#rfc.xref.status.203.3">C</a></li>
     4968                  <li>204 No Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.204.1">7.1</a>, <a href="#rfc.iref.56"><b>7.3.5</b></a>, <a href="#rfc.xref.status.204.2">10.2.3</a></li>
     4969                  <li>205 Reset Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.205.1">7.1</a>, <a href="#rfc.iref.56"><b>7.3.6</b></a>, <a href="#rfc.xref.status.205.2">10.2.3</a></li>
     4970                  <li>2xx Successful (status code class)&nbsp;&nbsp;<a href="#rfc.iref.55"><b>7.3</b></a></li>
    49794971               </ul>
    49804972            </li>
    49814973            <li><a id="rfc.index.3" href="#rfc.index.3"><b>3</b></a><ul>
    4982                   <li>300 Multiple Choices (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.300.1">7.1</a>, <a href="#rfc.iref.65"><b>7.4.1</b></a>, <a href="#rfc.xref.status.300.2">10.2.3</a></li>
    4983                   <li>301 Moved Permanently (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.301.1">7.1</a>, <a href="#rfc.iref.65"><b>7.4.2</b></a>, <a href="#rfc.xref.status.301.2">10.2.3</a>, <a href="#rfc.xref.status.301.3">C</a></li>
    4984                   <li>302 Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.302.1">7.1</a>, <a href="#rfc.iref.65"><b>7.4.3</b></a>, <a href="#rfc.xref.status.302.2">10.2.3</a>, <a href="#rfc.xref.status.302.3">C</a></li>
    4985                   <li>303 See Other (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.303.1">7.1</a>, <a href="#rfc.iref.65"><b>7.4.4</b></a>, <a href="#rfc.xref.status.303.2">10.2.3</a></li>
    4986                   <li>305 Use Proxy (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.305.1">7.1</a>, <a href="#rfc.iref.65"><b>7.4.5</b></a>, <a href="#rfc.xref.status.305.2">10.2.3</a>, <a href="#rfc.xref.status.305.3">C</a></li>
    4987                   <li>306 (Unused) (status code)&nbsp;&nbsp;<a href="#rfc.iref.65"><b>7.4.6</b></a>, <a href="#rfc.xref.status.306.1">10.2.3</a></li>
    4988                   <li>307 Temporary Redirect (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.307.1">7.1</a>, <a href="#rfc.iref.65"><b>7.4.7</b></a>, <a href="#rfc.xref.status.307.2">10.2.3</a>, <a href="#rfc.xref.status.307.3">C</a></li>
    4989                   <li>3xx Redirection (status code class)&nbsp;&nbsp;<a href="#rfc.iref.64"><b>7.4</b></a>, <a href="#rfc.xref.status.3xx.1">C</a></li>
     4974                  <li>300 Multiple Choices (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.300.1">7.1</a>, <a href="#rfc.iref.57"><b>7.4.1</b></a>, <a href="#rfc.xref.status.300.2">10.2.3</a></li>
     4975                  <li>301 Moved Permanently (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.301.1">7.1</a>, <a href="#rfc.iref.57"><b>7.4.2</b></a>, <a href="#rfc.xref.status.301.2">10.2.3</a>, <a href="#rfc.xref.status.301.3">C</a></li>
     4976                  <li>302 Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.302.1">7.1</a>, <a href="#rfc.iref.57"><b>7.4.3</b></a>, <a href="#rfc.xref.status.302.2">10.2.3</a>, <a href="#rfc.xref.status.302.3">C</a></li>
     4977                  <li>303 See Other (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.303.1">7.1</a>, <a href="#rfc.iref.57"><b>7.4.4</b></a>, <a href="#rfc.xref.status.303.2">10.2.3</a></li>
     4978                  <li>305 Use Proxy (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.305.1">7.1</a>, <a href="#rfc.iref.57"><b>7.4.5</b></a>, <a href="#rfc.xref.status.305.2">10.2.3</a>, <a href="#rfc.xref.status.305.3">C</a></li>
     4979                  <li>306 (Unused) (status code)&nbsp;&nbsp;<a href="#rfc.iref.57"><b>7.4.6</b></a>, <a href="#rfc.xref.status.306.1">10.2.3</a></li>
     4980                  <li>307 Temporary Redirect (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.307.1">7.1</a>, <a href="#rfc.iref.57"><b>7.4.7</b></a>, <a href="#rfc.xref.status.307.2">10.2.3</a>, <a href="#rfc.xref.status.307.3">C</a></li>
     4981                  <li>3xx Redirection (status code class)&nbsp;&nbsp;<a href="#rfc.iref.56"><b>7.4</b></a>, <a href="#rfc.xref.status.3xx.1">C</a></li>
    49904982               </ul>
    49914983            </li>
    49924984            <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul>
    4993                   <li>400 Bad Request (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.400.1">7.1</a>, <a href="#rfc.iref.66"><b>7.5.1</b></a>, <a href="#rfc.xref.status.400.2">10.2.3</a></li>
    4994                   <li>402 Payment Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.402.1">7.1</a>, <a href="#rfc.iref.66"><b>7.5.2</b></a>, <a href="#rfc.xref.status.402.2">10.2.3</a></li>
    4995                   <li>403 Forbidden (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.403.1">7.1</a>, <a href="#rfc.iref.66"><b>7.5.3</b></a>, <a href="#rfc.xref.status.403.2">10.2.3</a></li>
    4996                   <li>404 Not Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.404.1">7.1</a>, <a href="#rfc.iref.66"><b>7.5.4</b></a>, <a href="#rfc.xref.status.404.2">10.2.3</a></li>
    4997                   <li>405 Method Not Allowed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.405.1">7.1</a>, <a href="#rfc.iref.66"><b>7.5.5</b></a>, <a href="#rfc.xref.status.405.2">10.2.3</a></li>
    4998                   <li>406 Not Acceptable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.406.1">7.1</a>, <a href="#rfc.iref.66"><b>7.5.6</b></a>, <a href="#rfc.xref.status.406.2">10.2.3</a></li>
    4999                   <li>408 Request Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.408.1">7.1</a>, <a href="#rfc.iref.66"><b>7.5.7</b></a>, <a href="#rfc.xref.status.408.2">10.2.3</a></li>
    5000                   <li>409 Conflict (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.409.1">7.1</a>, <a href="#rfc.iref.66"><b>7.5.8</b></a>, <a href="#rfc.xref.status.409.2">10.2.3</a></li>
    5001                   <li>410 Gone (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.410.1">7.1</a>, <a href="#rfc.iref.66"><b>7.5.9</b></a>, <a href="#rfc.xref.status.410.2">10.2.3</a></li>
    5002                   <li>411 Length Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.411.1">7.1</a>, <a href="#rfc.iref.66"><b>7.5.10</b></a>, <a href="#rfc.xref.status.411.2">10.2.3</a></li>
    5003                   <li>413 Request Representation Too Large (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.413.1">7.1</a>, <a href="#rfc.iref.66"><b>7.5.11</b></a>, <a href="#rfc.xref.status.413.2">10.2.3</a></li>
    5004                   <li>414 URI Too Long (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.414.1">7.1</a>, <a href="#rfc.iref.66"><b>7.5.12</b></a>, <a href="#rfc.xref.status.414.2">10.2.3</a></li>
    5005                   <li>415 Unsupported Media Type (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.415.1">7.1</a>, <a href="#rfc.iref.66"><b>7.5.13</b></a>, <a href="#rfc.xref.status.415.2">10.2.3</a></li>
    5006                   <li>417 Expectation Failed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.417.1">7.1</a>, <a href="#rfc.iref.66"><b>7.5.14</b></a>, <a href="#rfc.xref.status.417.2">10.2.3</a></li>
    5007                   <li>426 Upgrade Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.426.1">7.1</a>, <a href="#rfc.iref.66"><b>7.5.15</b></a>, <a href="#rfc.xref.status.426.2">10.2.3</a>, <a href="#rfc.xref.status.426.3">C</a></li>
    5008                   <li>4xx Client Error (status code class)&nbsp;&nbsp;<a href="#rfc.iref.65"><b>7.5</b></a></li>
     4985                  <li>400 Bad Request (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.400.1">7.1</a>, <a href="#rfc.iref.58"><b>7.5.1</b></a>, <a href="#rfc.xref.status.400.2">10.2.3</a></li>
     4986                  <li>402 Payment Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.402.1">7.1</a>, <a href="#rfc.iref.58"><b>7.5.2</b></a>, <a href="#rfc.xref.status.402.2">10.2.3</a></li>
     4987                  <li>403 Forbidden (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.403.1">7.1</a>, <a href="#rfc.iref.58"><b>7.5.3</b></a>, <a href="#rfc.xref.status.403.2">10.2.3</a></li>
     4988                  <li>404 Not Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.404.1">7.1</a>, <a href="#rfc.iref.58"><b>7.5.4</b></a>, <a href="#rfc.xref.status.404.2">10.2.3</a></li>
     4989                  <li>405 Method Not Allowed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.405.1">7.1</a>, <a href="#rfc.iref.58"><b>7.5.5</b></a>, <a href="#rfc.xref.status.405.2">10.2.3</a></li>
     4990                  <li>406 Not Acceptable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.406.1">7.1</a>, <a href="#rfc.iref.58"><b>7.5.6</b></a>, <a href="#rfc.xref.status.406.2">10.2.3</a></li>
     4991                  <li>408 Request Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.408.1">7.1</a>, <a href="#rfc.iref.58"><b>7.5.7</b></a>, <a href="#rfc.xref.status.408.2">10.2.3</a></li>
     4992                  <li>409 Conflict (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.409.1">7.1</a>, <a href="#rfc.iref.58"><b>7.5.8</b></a>, <a href="#rfc.xref.status.409.2">10.2.3</a></li>
     4993                  <li>410 Gone (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.410.1">7.1</a>, <a href="#rfc.iref.58"><b>7.5.9</b></a>, <a href="#rfc.xref.status.410.2">10.2.3</a></li>
     4994                  <li>411 Length Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.411.1">7.1</a>, <a href="#rfc.iref.58"><b>7.5.10</b></a>, <a href="#rfc.xref.status.411.2">10.2.3</a></li>
     4995                  <li>413 Request Representation Too Large (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.413.1">7.1</a>, <a href="#rfc.iref.58"><b>7.5.11</b></a>, <a href="#rfc.xref.status.413.2">10.2.3</a></li>
     4996                  <li>414 URI Too Long (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.414.1">7.1</a>, <a href="#rfc.iref.58"><b>7.5.12</b></a>, <a href="#rfc.xref.status.414.2">10.2.3</a></li>
     4997                  <li>415 Unsupported Media Type (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.415.1">7.1</a>, <a href="#rfc.iref.58"><b>7.5.13</b></a>, <a href="#rfc.xref.status.415.2">10.2.3</a></li>
     4998                  <li>417 Expectation Failed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.417.1">7.1</a>, <a href="#rfc.iref.58"><b>7.5.14</b></a>, <a href="#rfc.xref.status.417.2">10.2.3</a></li>
     4999                  <li>426 Upgrade Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.426.1">7.1</a>, <a href="#rfc.iref.58"><b>7.5.15</b></a>, <a href="#rfc.xref.status.426.2">10.2.3</a>, <a href="#rfc.xref.status.426.3">C</a></li>
     5000                  <li>4xx Client Error (status code class)&nbsp;&nbsp;<a href="#rfc.iref.57"><b>7.5</b></a></li>
    50095001               </ul>
    50105002            </li>
    50115003            <li><a id="rfc.index.5" href="#rfc.index.5"><b>5</b></a><ul>
    5012                   <li>500 Internal Server Error (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.500.1">7.1</a>, <a href="#rfc.iref.67"><b>7.6.1</b></a>, <a href="#rfc.xref.status.500.2">10.2.3</a></li>
    5013                   <li>501 Not Implemented (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.501.1">7.1</a>, <a href="#rfc.iref.67"><b>7.6.2</b></a>, <a href="#rfc.xref.status.501.2">10.2.3</a></li>
    5014                   <li>502 Bad Gateway (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.502.1">7.1</a>, <a href="#rfc.iref.67"><b>7.6.3</b></a>, <a href="#rfc.xref.status.502.2">10.2.3</a></li>
    5015                   <li>503 Service Unavailable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.503.1">7.1</a>, <a href="#rfc.iref.67"><b>7.6.4</b></a>, <a href="#rfc.xref.status.503.2">10.2.3</a></li>
    5016                   <li>504 Gateway Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.504.1">7.1</a>, <a href="#rfc.iref.67"><b>7.6.5</b></a>, <a href="#rfc.xref.status.504.2">10.2.3</a></li>
    5017                   <li>505 HTTP Version Not Supported (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.505.1">7.1</a>, <a href="#rfc.iref.67"><b>7.6.6</b></a>, <a href="#rfc.xref.status.505.2">10.2.3</a></li>
    5018                   <li>5xx Server Error (status code class)&nbsp;&nbsp;<a href="#rfc.iref.66"><b>7.6</b></a></li>
     5004                  <li>500 Internal Server Error (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.500.1">7.1</a>, <a href="#rfc.iref.59"><b>7.6.1</b></a>, <a href="#rfc.xref.status.500.2">10.2.3</a></li>
     5005                  <li>501 Not Implemented (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.501.1">7.1</a>, <a href="#rfc.iref.59"><b>7.6.2</b></a>, <a href="#rfc.xref.status.501.2">10.2.3</a></li>
     5006                  <li>502 Bad Gateway (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.502.1">7.1</a>, <a href="#rfc.iref.59"><b>7.6.3</b></a>, <a href="#rfc.xref.status.502.2">10.2.3</a></li>
     5007                  <li>503 Service Unavailable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.503.1">7.1</a>, <a href="#rfc.iref.59"><b>7.6.4</b></a>, <a href="#rfc.xref.status.503.2">10.2.3</a></li>
     5008                  <li>504 Gateway Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.504.1">7.1</a>, <a href="#rfc.iref.59"><b>7.6.5</b></a>, <a href="#rfc.xref.status.504.2">10.2.3</a></li>
     5009                  <li>505 HTTP Version Not Supported (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.505.1">7.1</a>, <a href="#rfc.iref.59"><b>7.6.6</b></a>, <a href="#rfc.xref.status.505.2">10.2.3</a></li>
     5010                  <li>5xx Server Error (status code class)&nbsp;&nbsp;<a href="#rfc.iref.58"><b>7.6</b></a></li>
    50195011               </ul>
    50205012            </li>
     
    51475139            </li>
    51485140            <li><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul>
    5149                   <li>Max-Forwards header field&nbsp;&nbsp;<a href="#rfc.xref.header.max-forwards.1">5.3.7</a>, <a href="#rfc.xref.header.max-forwards.2">5.3.8</a>, <a href="#rfc.xref.header.max-forwards.3">6.1</a>, <a href="#rfc.iref.m.9"><b>6.1.1</b></a>, <a href="#rfc.xref.header.max-forwards.4">10.3.2</a>, <a href="#rfc.xref.header.max-forwards.5">C</a></li>
    5150                   <li>Methods&nbsp;&nbsp;
    5151                      <ul>
    5152                         <li>CONNECT&nbsp;&nbsp;<a href="#rfc.xref.CONNECT.1">5.1</a>, <a href="#rfc.iref.m.6"><b>5.3.6</b></a>, <a href="#rfc.xref.CONNECT.2">10.1.3</a>, <a href="#rfc.xref.CONNECT.3">C</a></li>
    5153                         <li>DELETE&nbsp;&nbsp;<a href="#rfc.xref.DELETE.1">5.1</a>, <a href="#rfc.iref.m.5"><b>5.3.5</b></a>, <a href="#rfc.xref.DELETE.2">10.1.3</a></li>
    5154                         <li>GET&nbsp;&nbsp;<a href="#rfc.xref.GET.1">3</a>, <a href="#rfc.xref.GET.2">5.1</a>, <a href="#rfc.iref.m.1"><b>5.3.1</b></a>, <a href="#rfc.xref.GET.3">10.1.3</a></li>
    5155                         <li>HEAD&nbsp;&nbsp;<a href="#rfc.xref.HEAD.1">5.1</a>, <a href="#rfc.iref.m.2"><b>5.3.2</b></a>, <a href="#rfc.xref.HEAD.2">10.1.3</a></li>
    5156                         <li>OPTIONS&nbsp;&nbsp;<a href="#rfc.xref.OPTIONS.1">5.1</a>, <a href="#rfc.iref.m.7"><b>5.3.7</b></a>, <a href="#rfc.xref.OPTIONS.2">6.1.1</a>, <a href="#rfc.xref.OPTIONS.3">10.1.3</a></li>
    5157                         <li>POST&nbsp;&nbsp;<a href="#rfc.xref.POST.1">3</a>, <a href="#rfc.xref.POST.2">5.1</a>, <a href="#rfc.iref.m.3"><b>5.3.3</b></a>, <a href="#rfc.xref.POST.3">10.1.3</a>, <a href="#rfc.xref.POST.4">C</a></li>
    5158                         <li>PUT&nbsp;&nbsp;<a href="#rfc.xref.PUT.1">3</a>, <a href="#rfc.xref.PUT.2">5.1</a>, <a href="#rfc.iref.m.4"><b>5.3.4</b></a>, <a href="#rfc.xref.PUT.3">10.1.3</a>, <a href="#rfc.xref.PUT.4">C</a></li>
    5159                         <li>TRACE&nbsp;&nbsp;<a href="#rfc.xref.TRACE.1">5.1</a>, <a href="#rfc.iref.m.8"><b>5.3.8</b></a>, <a href="#rfc.xref.TRACE.2">6.1.1</a>, <a href="#rfc.xref.TRACE.3">10.1.3</a>, <a href="#rfc.xref.TRACE.4">11.1</a></li>
    5160                      </ul>
    5161                   </li>
    5162                   <li>MIME-Version header field&nbsp;&nbsp;<a href="#rfc.xref.mime-version.1">10.3.2</a>, <a href="#rfc.iref.m.10"><b>A.1</b></a></li>
     5141                  <li>Max-Forwards header field&nbsp;&nbsp;<a href="#rfc.xref.header.max-forwards.1">5.3.7</a>, <a href="#rfc.xref.header.max-forwards.2">5.3.8</a>, <a href="#rfc.xref.header.max-forwards.3">6.1</a>, <a href="#rfc.iref.m.1"><b>6.1.1</b></a>, <a href="#rfc.xref.header.max-forwards.4">10.3.2</a>, <a href="#rfc.xref.header.max-forwards.5">C</a></li>
     5142                  <li>MIME-Version header field&nbsp;&nbsp;<a href="#rfc.xref.mime-version.1">10.3.2</a>, <a href="#rfc.iref.m.2"><b>A.1</b></a></li>
    51635143               </ul>
    51645144            </li>
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1895 r1898  
    10941094  </rdf:Description>
    10951095  <iref primary="true" item="GET method" x:for-anchor=""/>
    1096   <iref primary="true" item="Methods" subitem="GET" x:for-anchor=""/>
    10971096<t>
    10981097   The GET method requests transfer of a current representation of
     
    11451144  </rdf:Description>
    11461145  <iref primary="true" item="HEAD method" x:for-anchor=""/>
    1147   <iref primary="true" item="Methods" subitem="HEAD" x:for-anchor=""/>
    11481146<t>
    11491147   The HEAD method is identical to GET except that the server &MUST-NOT;
     
    11701168<section title="POST" anchor="POST">
    11711169  <iref primary="true" item="POST method" x:for-anchor=""/>
    1172   <iref primary="true" item="Methods" subitem="POST" x:for-anchor=""/>
    11731170<t>
    11741171   The POST method requests that the origin server accept the
     
    12291226  </rdf:Description>
    12301227  <iref primary="true" item="PUT method" x:for-anchor=""/>
    1231   <iref primary="true" item="Methods" subitem="PUT" x:for-anchor=""/>
    12321228<t>
    12331229   The PUT method requests that the state of the target resource
     
    13571353  </rdf:Description>
    13581354  <iref primary="true" item="DELETE method" x:for-anchor=""/>
    1359   <iref primary="true" item="Methods" subitem="DELETE" x:for-anchor=""/>
    13601355<t>
    13611356   The DELETE method requests that the origin server delete the target
     
    13901385<section title="CONNECT" anchor="CONNECT">
    13911386  <iref primary="true" item="CONNECT method" x:for-anchor=""/>
    1392   <iref primary="true" item="Methods" subitem="CONNECT" x:for-anchor=""/>
    13931387<t>
    13941388   The CONNECT method requests that the proxy establish a tunnel
     
    14761470  </rdf:Description>
    14771471  <iref primary="true" item="OPTIONS method" x:for-anchor=""/>
    1478   <iref primary="true" item="Methods" subitem="OPTIONS" x:for-anchor=""/>
    14791472<t>
    14801473   The OPTIONS method requests information about the
     
    15371530  </rdf:Description>
    15381531  <iref primary="true" item="TRACE method" x:for-anchor=""/>
    1539   <iref primary="true" item="Methods" subitem="TRACE" x:for-anchor=""/>
    15401532<t>
    15411533   The TRACE method requests a remote, application-level loop-back
Note: See TracChangeset for help on using the changeset viewer.