Ignore:
Timestamp:
Nov 14, 2008, 4:44:55 PM (11 years ago)
Author:
julian.reschke@…
Message:

Merge in Roy's changes wrt Introduction and HTTP Architecture, replace Request-URI by request-target and relative-URI by partial-URI throughout.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.html

    r386 r391  
    477477         <tr>
    478478            <td class="header left"></td>
    479             <td class="header right">November 14, 2008</td>
     479            <td class="header right">November 15, 2008</td>
    480480         </tr>
    481481      </table>
     
    588588                     <li class="tocline1">9.4.13&nbsp;&nbsp;&nbsp;<a href="#status.412">412 Precondition Failed</a></li>
    589589                     <li class="tocline1">9.4.14&nbsp;&nbsp;&nbsp;<a href="#status.413">413 Request Entity Too Large</a></li>
    590                      <li class="tocline1">9.4.15&nbsp;&nbsp;&nbsp;<a href="#status.414">414 Request-URI Too Long</a></li>
     590                     <li class="tocline1">9.4.15&nbsp;&nbsp;&nbsp;<a href="#status.414">414 Request-target Too Long</a></li>
    591591                     <li class="tocline1">9.4.16&nbsp;&nbsp;&nbsp;<a href="#status.415">415 Unsupported Media Type</a></li>
    592592                     <li class="tocline1">9.4.17&nbsp;&nbsp;&nbsp;<a href="#status.416">416 Requested Range Not Satisfiable</a></li>
     
    673673      </p>
    674674      <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="notation" href="#notation">Notational Conventions and Generic Grammar</a></h1>
    675       <p id="rfc.section.2.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation.abnf" title="ABNF Extension: #rule">Section 2.1</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> and the core rules defined in <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a> of <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>:
    676       </p>
    677       <div id="rfc.figure.u.1"></div><pre class="inline">  <a href="#notation" class="smpl">CR</a>            = &lt;CR, defined in <a href="#Part1" id="rfc.xref.Part1.4"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>&gt;
    678   <a href="#notation" class="smpl">DIGIT</a>         = &lt;DIGIT, defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>&gt;
    679   <a href="#notation" class="smpl">LF</a>            = &lt;LF, defined in <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>&gt;
    680 </pre><div id="rfc.figure.u.2"></div><pre class="inline">  <a href="#notation" class="smpl">comment</a>       = &lt;comment, defined in <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>&gt;
    681   <a href="#notation" class="smpl">quoted-string</a> = &lt;quoted-string, defined in <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>&gt;
    682   <a href="#notation" class="smpl">token</a>         = &lt;token, defined in <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>&gt;
    683   <a href="#notation" class="smpl">OWS</a>           = &lt;OWS, defined in <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>&gt;
    684   <a href="#notation" class="smpl">RWS</a>           = &lt;RWS, defined in <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>&gt;
    685   <a href="#notation" class="smpl">TEXT</a>          = &lt;TEXT, defined in <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>&gt;
     675      <p id="rfc.section.2.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation.abnf" title="ABNF Extension: #rule">Section 1.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> and the core rules defined in <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>:
     676      </p>
     677      <div id="rfc.figure.u.1"></div><pre class="inline">  <a href="#notation" class="smpl">CR</a>            = &lt;CR, defined in <a href="#Part1" id="rfc.xref.Part1.4"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
     678  <a href="#notation" class="smpl">DIGIT</a>         = &lt;DIGIT, defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
     679  <a href="#notation" class="smpl">LF</a>            = &lt;LF, defined in <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
     680</pre><div id="rfc.figure.u.2"></div><pre class="inline">  <a href="#notation" class="smpl">comment</a>       = &lt;comment, defined in <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
     681  <a href="#notation" class="smpl">quoted-string</a> = &lt;quoted-string, defined in <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
     682  <a href="#notation" class="smpl">token</a>         = &lt;token, defined in <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
     683  <a href="#notation" class="smpl">OWS</a>           = &lt;OWS, defined in <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
     684  <a href="#notation" class="smpl">RWS</a>           = &lt;RWS, defined in <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
     685  <a href="#notation" class="smpl">TEXT</a>          = &lt;TEXT, defined in <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
    686686</pre><div id="abnf.dependencies">
    687687         <p id="rfc.section.2.p.4">                                                  The ABNF rules below are defined in other parts:</p>
    688688      </div>
    689       <div id="rfc.figure.u.3"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">absolute-URI</a>  = &lt;absolute-URI, defined in <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 3.2</a>&gt;
    690   <a href="#abnf.dependencies" class="smpl">fragment</a>      = &lt;fragment, defined in <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 3.2</a>&gt;
    691   <a href="#abnf.dependencies" class="smpl">Host</a>          = &lt;Host, defined in <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 3.2</a>&gt;
    692   <a href="#abnf.dependencies" class="smpl">HTTP-date</a>     = &lt;HTTP-date, defined in <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#full.date" title="Full Date">Section 3.3.1</a>&gt;
    693   <a href="#abnf.dependencies" class="smpl">product</a>       = &lt;product, defined in <a href="#Part1" id="rfc.xref.Part1.17"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 3.5</a>&gt;
    694   <a href="#abnf.dependencies" class="smpl">relativeURI</a>   = &lt;relativeURI, defined in <a href="#Part1" id="rfc.xref.Part1.18"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 3.2</a>&gt;
     689      <div id="rfc.figure.u.3"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">absolute-URI</a>  = &lt;absolute-URI, defined in <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.1</a>&gt;
     690  <a href="#abnf.dependencies" class="smpl">fragment</a>      = &lt;fragment, defined in <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.1</a>&gt;
     691  <a href="#abnf.dependencies" class="smpl">Host</a>          = &lt;Host, defined in <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.1</a>&gt;
     692  <a href="#abnf.dependencies" class="smpl">HTTP-date</a>     = &lt;HTTP-date, defined in <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#full.date" title="Full Date">Section 3.2.1</a>&gt;
     693  <a href="#abnf.dependencies" class="smpl">partial-URI</a>   = &lt;partial-URI, defined in <a href="#Part1" id="rfc.xref.Part1.17"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.1</a>&gt;
     694  <a href="#abnf.dependencies" class="smpl">product</a>       = &lt;product, defined in <a href="#Part1" id="rfc.xref.Part1.18"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 3.4</a>&gt;
    695695  <a href="#abnf.dependencies" class="smpl">TE</a>            = &lt;TE, defined in <a href="#Part1" id="rfc.xref.Part1.19"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 8.8</a>&gt;
    696696</pre><div id="rfc.figure.u.4"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">Accept</a>        = &lt;Accept, defined in <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept" title="Accept">Section 6.1</a>&gt;
     
    721721             &lt;WWW-Authenticate, defined in <a href="#Part7" id="rfc.xref.Part7.4"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.www-authenticate" title="WWW-Authenticate">Section 4.4</a>&gt;
    722722</pre><h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="method" href="#method">Method</a></h1>
    723       <p id="rfc.section.3.p.1">The Method token indicates the method to be performed on the resource identified by the Request-URI. The method is case-sensitive.</p>
     723      <p id="rfc.section.3.p.1">The Method token indicates the method to be performed on the resource identified by the request-target. The method is case-sensitive.</p>
    724724      <div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span>  <a href="#method" class="smpl">Method</a>         = %x4F.50.54.49.4F.4E.53   ; "OPTIONS", <a href="#OPTIONS" id="rfc.xref.OPTIONS.1" title="OPTIONS">Section&nbsp;8.2</a>
    725725                 / %x47.45.54               ; "GET", <a href="#GET" id="rfc.xref.GET.1" title="GET">Section&nbsp;8.3</a>
     
    820820       / "412"  ; <a href="#status.412" id="rfc.xref.status.412.1" title="412 Precondition Failed">Section&nbsp;9.4.13</a>: Precondition Failed
    821821       / "413"  ; <a href="#status.413" id="rfc.xref.status.413.1" title="413 Request Entity Too Large">Section&nbsp;9.4.14</a>: Request Entity Too Large
    822        / "414"  ; <a href="#status.414" id="rfc.xref.status.414.1" title="414 Request-URI Too Long">Section&nbsp;9.4.15</a>: Request-URI Too Large
     822       / "414"  ; <a href="#status.414" id="rfc.xref.status.414.1" title="414 Request-target Too Long">Section&nbsp;9.4.15</a>: Request-target Too Large
    823823       / "415"  ; <a href="#status.415" id="rfc.xref.status.415.1" title="415 Unsupported Media Type">Section&nbsp;9.4.16</a>: Unsupported Media Type
    824824       / "416"  ; <a href="#status.416" id="rfc.xref.status.416.1" title="416 Requested Range Not Satisfiable">Section&nbsp;9.4.17</a>: Requested range not satisfiable
     
    850850      <p id="rfc.section.6.p.1">The response-header fields allow the server to pass additional information about the response which cannot be placed in the
    851851         Status-Line. These header fields give information about the server and about further access to the resource identified by
    852          the Request-URI.
     852         the request-target.
    853853      </p>
    854854      <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.7"></span>  <a href="#response.header.fields" class="smpl">response-header</a> = <a href="#abnf.dependencies" class="smpl">Accept-Ranges</a>           ; <a href="#Part5" id="rfc.xref.Part5.6"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.accept-ranges" title="Accept-Ranges">Section 6.1</a>
     
    910910      <div id="rfc.iref.m.1"></div>
    911911      <p id="rfc.section.8.2.p.1">The OPTIONS method represents a request for information about the communication options available on the request/response
    912          chain identified by the Request-URI. This method allows the client to determine the options and/or requirements associated
     912         chain identified by the request-target. This method allows the client to determine the options and/or requirements associated
    913913         with a resource, or the capabilities of a server, without implying a resource action or initiating a resource retrieval.
    914914      </p>
     
    918918         to HTTP might use the OPTIONS body to make more detailed queries on the server.
    919919      </p>
    920       <p id="rfc.section.8.2.p.4">If the Request-URI is an asterisk ("*"), the OPTIONS request is intended to apply to the server in general rather than to
    921          a specific resource. Since a server's communication options typically depend on the resource, the "*" request is only useful
     920      <p id="rfc.section.8.2.p.4">If the request-target is an asterisk ("*"), the OPTIONS request is intended to apply to the server in general rather than
     921         to a specific resource. Since a server's communication options typically depend on the resource, the "*" request is only useful
    922922         as a "ping" or "no-op" type of method; it does nothing beyond allowing the client to test the capabilities of the server.
    923923         For example, this can be used to test a proxy for HTTP/1.1 compliance (or lack thereof).
    924924      </p>
    925       <p id="rfc.section.8.2.p.5">If the Request-URI is not an asterisk, the OPTIONS request applies only to the options that are available when communicating
     925      <p id="rfc.section.8.2.p.5">If the request-target is not an asterisk, the OPTIONS request applies only to the options that are available when communicating
    926926         with that resource.
    927927      </p>
     
    937937      <div id="rfc.iref.g.8"></div>
    938938      <div id="rfc.iref.m.2"></div>
    939       <p id="rfc.section.8.3.p.1">The GET method means retrieve whatever information (in the form of an entity) is identified by the Request-URI. If the Request-URI
    940          refers to a data-producing process, it is the produced data which shall be returned as the entity in the response and not
    941          the source text of the process, unless that text happens to be the output of the process.
     939      <p id="rfc.section.8.3.p.1">The GET method means retrieve whatever information (in the form of an entity) is identified by the request-target. If the
     940         request-target refers to a data-producing process, it is the produced data which shall be returned as the entity in the response
     941         and not the source text of the process, unless that text happens to be the output of the process.
    942942      </p>
    943943      <p id="rfc.section.8.3.p.2">The semantics of the GET method change to a "conditional GET" if the request message includes an If-Modified-Since, If-Unmodified-Since,
     
    970970      <h2 id="rfc.section.8.5"><a href="#rfc.section.8.5">8.5</a>&nbsp;<a id="POST" href="#POST">POST</a></h2>
    971971      <p id="rfc.section.8.5.p.1">The POST method is used to request that the origin server accept the entity enclosed in the request as data to be processed
    972          by the resource identified by the Request-URI in the Request-Line. POST is designed to allow a uniform method to cover the
    973          following functions:
     972         by the resource identified by the request-target in the Request-Line. POST is designed to allow a uniform method to cover
     973         the following functions:
    974974      </p>
    975975      <ul>
     
    979979         <li>Extending a database through an append operation.</li>
    980980      </ul>
    981       <p id="rfc.section.8.5.p.2">The actual function performed by the POST method is determined by the server and is usually dependent on the Request-URI.</p>
     981      <p id="rfc.section.8.5.p.2">The actual function performed by the POST method is determined by the server and is usually dependent on the request-target.</p>
    982982      <p id="rfc.section.8.5.p.3">The action performed by the POST method might not result in a resource that can be identified by a URI. In this case, either
    983983         200 (OK) or 204 (No Content) is the appropriate response status, depending on whether or not the response includes an entity
     
    993993      <div id="rfc.iref.m.5"></div>
    994994      <h2 id="rfc.section.8.6"><a href="#rfc.section.8.6">8.6</a>&nbsp;<a id="PUT" href="#PUT">PUT</a></h2>
    995       <p id="rfc.section.8.6.p.1">The PUT method requests that the enclosed entity be stored at the supplied Request-URI. If the Request-URI refers to an already
    996          existing resource, the enclosed entity <em class="bcp14">SHOULD</em> be considered as a modified version of the one residing on the origin server. If the Request-URI does not point to an existing
     995      <p id="rfc.section.8.6.p.1">The PUT method requests that the enclosed entity be stored at the supplied request-target. If the request-target refers to
     996         an already existing resource, the enclosed entity <em class="bcp14">SHOULD</em> be considered as a modified version of the one residing on the origin server. If the request-target does not point to an existing
    997997         resource, and that URI is capable of being defined as a new resource by the requesting user agent, the origin server can create
    998          the resource with that URI. If a new resource is created at the Request-URI, the origin server <em class="bcp14">MUST</em> inform the user agent via the 201 (Created) response. If an existing resource is modified, either the 200 (OK) or 204 (No
    999          Content) response codes <em class="bcp14">SHOULD</em> be sent to indicate successful completion of the request. If the resource could not be created or modified with the Request-URI,
     998         the resource with that URI. If a new resource is created at the request-target, the origin server <em class="bcp14">MUST</em> inform the user agent via the 201 (Created) response. If an existing resource is modified, either the 200 (OK) or 204 (No
     999         Content) response codes <em class="bcp14">SHOULD</em> be sent to indicate successful completion of the request. If the resource could not be created or modified with the request-target,
    10001000         an appropriate error response <em class="bcp14">SHOULD</em> be given that reflects the nature of the problem. The recipient of the entity <em class="bcp14">MUST NOT</em> ignore any Content-* headers (headers starting with the prefix 'Content-') that it does not understand or implement and <em class="bcp14">MUST</em> return a 501 (Not Implemented) response in such cases.
    10011001      </p>
    1002       <p id="rfc.section.8.6.p.2">If the request passes through a cache and the Request-URI identifies one or more currently cached entities, those entries <em class="bcp14">SHOULD</em> be treated as stale. Responses to this method are not cacheable.
    1003       </p>
    1004       <p id="rfc.section.8.6.p.3">The fundamental difference between the POST and PUT requests is reflected in the different meaning of the Request-URI. The
    1005          URI in a POST request identifies the resource that will handle the enclosed entity. That resource might be a data-accepting
     1002      <p id="rfc.section.8.6.p.2">If the request passes through a cache and the request-target identifies one or more currently cached entities, those entries <em class="bcp14">SHOULD</em> be treated as stale. Responses to this method are not cacheable.
     1003      </p>
     1004      <p id="rfc.section.8.6.p.3">The fundamental difference between the POST and PUT requests is reflected in the different meaning of the request-target.
     1005         The URI in a POST request identifies the resource that will handle the enclosed entity. That resource might be a data-accepting
    10061006         process, a gateway to some other protocol, or a separate entity that accepts annotations. In contrast, the URI in a PUT request
    10071007         identifies the entity enclosed with the request -- the user agent knows what URI is intended and the server <em class="bcp14">MUST NOT</em> attempt to apply the request to some other resource. If the server desires that the request be applied to a different URI,
     
    10181018      <div id="rfc.iref.m.6"></div>
    10191019      <h2 id="rfc.section.8.7"><a href="#rfc.section.8.7">8.7</a>&nbsp;<a id="DELETE" href="#DELETE">DELETE</a></h2>
    1020       <p id="rfc.section.8.7.p.1">The DELETE method requests that the origin server delete the resource identified by the Request-URI. 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
     1020      <p id="rfc.section.8.7.p.1">The DELETE method requests that the origin server delete the resource identified by the request-target. 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
    10211021         has been carried out, even if the status code returned from the origin server indicates that the action has been completed
    10221022         successfully. However, the server <em class="bcp14">SHOULD NOT</em> indicate success unless, at the time the response is given, it intends to delete the resource or move it to an inaccessible
     
    10261026         or 204 (No Content) if the action has been enacted but the response does not include an entity.
    10271027      </p>
    1028       <p id="rfc.section.8.7.p.3">If the request passes through a cache and the Request-URI identifies one or more currently cached entities, those entries <em class="bcp14">SHOULD</em> be treated as stale. Responses to this method are not cacheable.
     1028      <p id="rfc.section.8.7.p.3">If the request passes through a cache and the request-target identifies one or more currently cached entities, those entries <em class="bcp14">SHOULD</em> be treated as stale. Responses to this method are not cacheable.
    10291029      </p>
    10301030      <h2 id="rfc.section.8.8"><a href="#rfc.section.8.8">8.8</a>&nbsp;<a id="TRACE" href="#TRACE">TRACE</a></h2>
     
    11811181      <div id="rfc.iref.s.12"></div>
    11821182      <h3 id="rfc.section.9.3.2"><a href="#rfc.section.9.3.2">9.3.2</a>&nbsp;<a id="status.301" href="#status.301">301 Moved Permanently</a></h3>
    1183       <p id="rfc.section.9.3.2.p.1">The requested 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 Request-URI
     1183      <p id="rfc.section.9.3.2.p.1">The requested 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 request-target
    11841184         to one or more of the new references returned by the server, where possible. This response is cacheable unless indicated otherwise.
    11851185      </p>
     
    11981198      <h3 id="rfc.section.9.3.3"><a href="#rfc.section.9.3.3">9.3.3</a>&nbsp;<a id="status.302" href="#status.302">302 Found</a></h3>
    11991199      <p id="rfc.section.9.3.3.p.1">The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the
    1200          client <em class="bcp14">SHOULD</em> continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires
    1201          header field.
     1200         client <em class="bcp14">SHOULD</em> continue to use the request-target for future requests. This response is only cacheable if indicated by a Cache-Control or
     1201         Expires header field.
    12021202      </p>
    12031203      <p id="rfc.section.9.3.3.p.2">The temporary URI <em class="bcp14">SHOULD</em> be given by the Location field in the response. Unless the request method was HEAD, the entity of the response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the new URI(s).
     
    12521252      <div id="rfc.iref.s.18"></div>
    12531253      <h3 id="rfc.section.9.3.8"><a href="#rfc.section.9.3.8">9.3.8</a>&nbsp;<a id="status.307" href="#status.307">307 Temporary Redirect</a></h3>
    1254       <p id="rfc.section.9.3.8.p.1">The requested resource resides temporarily under a different URI. Since the redirection <em class="bcp14">MAY</em> be altered on occasion, the client <em class="bcp14">SHOULD</em> continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires
    1255          header field.
     1254      <p id="rfc.section.9.3.8.p.1">The requested resource resides temporarily under a different URI. Since the redirection <em class="bcp14">MAY</em> be altered on occasion, the client <em class="bcp14">SHOULD</em> continue to use the request-target for future requests. This response is only cacheable if indicated by a Cache-Control or
     1255         Expires header field.
    12561256      </p>
    12571257      <p id="rfc.section.9.3.8.p.2">The temporary URI <em class="bcp14">SHOULD</em> be given by the Location field in the response. Unless the request method was HEAD, the entity of the response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the new URI(s) , since many pre-HTTP/1.1 user agents do not understand
     
    12951295      <div id="rfc.iref.s.23"></div>
    12961296      <h3 id="rfc.section.9.4.5"><a href="#rfc.section.9.4.5">9.4.5</a>&nbsp;<a id="status.404" href="#status.404">404 Not Found</a></h3>
    1297       <p id="rfc.section.9.4.5.p.1">The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or
    1298          permanent. The 410 (Gone) status code <em class="bcp14">SHOULD</em> be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable
     1297      <p id="rfc.section.9.4.5.p.1">The server has not found anything matching the request-target. No indication is given of whether the condition is temporary
     1298         or permanent. The 410 (Gone) status code <em class="bcp14">SHOULD</em> be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable
    12991299         and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request
    13001300         has been refused, or when no other response is applicable.
     
    13031303      <div id="rfc.iref.s.24"></div>
    13041304      <h3 id="rfc.section.9.4.6"><a href="#rfc.section.9.4.6">9.4.6</a>&nbsp;<a id="status.405" href="#status.405">405 Method Not Allowed</a></h3>
    1305       <p id="rfc.section.9.4.6.p.1">The method specified in the Request-Line is not allowed for the resource identified by the Request-URI. The response <em class="bcp14">MUST</em> include an Allow header containing a list of valid methods for the requested resource.
     1305      <p id="rfc.section.9.4.6.p.1">The method specified in the Request-Line is not allowed for the resource identified by the request-target. The response <em class="bcp14">MUST</em> include an Allow header containing a list of valid methods for the requested resource.
    13061306      </p>
    13071307      <div id="rfc.iref.48"></div>
     
    13501350      <h3 id="rfc.section.9.4.11"><a href="#rfc.section.9.4.11">9.4.11</a>&nbsp;<a id="status.410" href="#status.410">410 Gone</a></h3>
    13511351      <p id="rfc.section.9.4.11.p.1">The requested resource is no longer available at the server and no forwarding address is known. This condition is expected
    1352          to be considered permanent. Clients with link editing capabilities <em class="bcp14">SHOULD</em> delete references to the Request-URI after user approval. If the server does not know, or has no facility to determine, whether
    1353          or not the condition is permanent, the status code 404 (Not Found) <em class="bcp14">SHOULD</em> be used instead. This response is cacheable unless indicated otherwise.
     1352         to be considered permanent. Clients with link editing capabilities <em class="bcp14">SHOULD</em> delete references to the request-target after user approval. If the server does not know, or has no facility to determine,
     1353         whether or not the condition is permanent, the status code 404 (Not Found) <em class="bcp14">SHOULD</em> be used instead. This response is cacheable unless indicated otherwise.
    13541354      </p>
    13551355      <p id="rfc.section.9.4.11.p.2">The 410 response is primarily intended to assist the task of web maintenance by notifying the recipient that the resource
     
    13811381      <div id="rfc.iref.56"></div>
    13821382      <div id="rfc.iref.s.33"></div>
    1383       <h3 id="rfc.section.9.4.15"><a href="#rfc.section.9.4.15">9.4.15</a>&nbsp;<a id="status.414" href="#status.414">414 Request-URI Too Long</a></h3>
    1384       <p id="rfc.section.9.4.15.p.1">The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret. This
    1385          rare condition is only likely to occur when a client has improperly converted a POST request to a GET request with long query
    1386          information, when the client has descended into a URI "black hole" of redirection (e.g., a redirected URI prefix that points
    1387          to a suffix of itself), or when the server is under attack by a client attempting to exploit security holes present in some
    1388          servers using fixed-length buffers for reading or manipulating the Request-URI.
     1383      <h3 id="rfc.section.9.4.15"><a href="#rfc.section.9.4.15">9.4.15</a>&nbsp;<a id="status.414" href="#status.414">414 Request-target Too Long</a></h3>
     1384      <p id="rfc.section.9.4.15.p.1">The server is refusing to service the request because the request-target is longer than the server is willing to interpret.
     1385         This rare condition is only likely to occur when a client has improperly converted a POST request to a GET request with long
     1386         query information, when the client has descended into a URI "black hole" of redirection (e.g., a redirected URI prefix that
     1387         points to a suffix of itself), or when the server is under attack by a client attempting to exploit security holes present
     1388         in some servers using fixed-length buffers for reading or manipulating the request-target.
    13891389      </p>
    13901390      <div id="rfc.iref.57"></div>
     
    14621462      <div id="rfc.iref.h.2"></div>
    14631463      <h2 id="rfc.section.10.1"><a href="#rfc.section.10.1">10.1</a>&nbsp;<a id="header.allow" href="#header.allow">Allow</a></h2>
    1464       <p id="rfc.section.10.1.p.1">The response-header field "Allow" lists the set of methods advertised as supported by the resource identified by the Request-URI.
     1464      <p id="rfc.section.10.1.p.1">The response-header field "Allow" lists the set of methods advertised as supported by the resource identified by the request-target.
    14651465         The purpose of this field is strictly to inform the recipient of valid methods associated with the resource. An Allow header
    14661466         field <em class="bcp14">MUST</em> be present in a 405 (Method Not Allowed) response.
     
    15261526      <h2 id="rfc.section.10.4"><a href="#rfc.section.10.4">10.4</a>&nbsp;<a id="header.location" href="#header.location">Location</a></h2>
    15271527      <p id="rfc.section.10.4.p.1">The response-header field "Location" is used for the identification of a new resource or to redirect the recipient to a location
    1528          other than the Request-URI for completion of the request. For 201 (Created) responses, the Location is that of the new resource
    1529          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. The field value consists of a single absolute
     1528         other than the request-target for completion of the request. For 201 (Created) responses, the Location is that of the new
     1529         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. The field value consists of a single absolute
    15301530         URI.
    15311531      </p>
     
    15661566      <h2 id="rfc.section.10.6"><a href="#rfc.section.10.6">10.6</a>&nbsp;<a id="header.referer" href="#header.referer">Referer</a></h2>
    15671567      <p id="rfc.section.10.6.p.1">The request-header field "Referer" [sic] allows the client to specify, for the server's benefit, the address (URI) of the
    1568          resource from which the Request-URI was obtained (the "referrer", although the header field is misspelled.) The Referer request-header
    1569          allows a server to generate lists of back-links to resources for interest, logging, optimized caching, etc. It also allows
    1570          obsolete or mistyped links to be traced for maintenance. The Referer field <em class="bcp14">MUST NOT</em> be sent if the Request-URI was obtained from a source that does not have its own URI, such as input from the user keyboard.
     1568         resource from which the request-target was obtained (the "referrer", although the header field is misspelled.) The Referer
     1569         request-header allows a server to generate lists of back-links to resources for interest, logging, optimized caching, etc.
     1570         It also allows obsolete or mistyped links to be traced for maintenance. The Referer field <em class="bcp14">MUST NOT</em> be sent if the request-target was obtained from a source that does not have its own URI, such as input from the user keyboard.
    15711571      </p>
    15721572      <div id="rfc.figure.u.21"></div><pre class="inline"><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span>  <a href="#header.referer" class="smpl">Referer</a>        = "Referer" ":" <a href="#notation" class="smpl">OWS</a> <a href="#header.referer" class="smpl">Referer-v</a>
    1573   <a href="#header.referer" class="smpl">Referer-v</a>      = <a href="#abnf.dependencies" class="smpl">absolute-URI</a> / <a href="#abnf.dependencies" class="smpl">relativeURI</a>
     1573  <a href="#header.referer" class="smpl">Referer-v</a>      = <a href="#abnf.dependencies" class="smpl">absolute-URI</a> / <a href="#abnf.dependencies" class="smpl">partial-URI</a>
    15741574</pre><p id="rfc.section.10.6.p.3">Example:</p>
    15751575      <div id="rfc.figure.u.22"></div><pre class="text">  Referer: http://www.example.org/hypertext/Overview.html
    1576 </pre><p id="rfc.section.10.6.p.5">If the field value is a relative URI, it <em class="bcp14">SHOULD</em> be interpreted relative to the Request-URI. The URI <em class="bcp14">MUST NOT</em> include a fragment. See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section&nbsp;12.2</a> for security considerations.
     1576</pre><p id="rfc.section.10.6.p.5">If the field value is a relative URI, it <em class="bcp14">SHOULD</em> be interpreted relative to the request-target. The URI <em class="bcp14">MUST NOT</em> include a fragment. See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section&nbsp;12.2</a> for security considerations.
    15771577      </p>
    15781578      <div id="rfc.iref.r.2"></div>
     
    15981598      <h2 id="rfc.section.10.8"><a href="#rfc.section.10.8">10.8</a>&nbsp;<a id="header.server" href="#header.server">Server</a></h2>
    15991599      <p id="rfc.section.10.8.p.1">The response-header field "Server" contains information about the software used by the origin server to handle the request.
    1600          The field can contain multiple product tokens (<a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 3.5</a> of <a href="#Part1" id="rfc.xref.Part1.28"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and comments identifying the server and any significant subproducts. The product tokens are listed in order of their significance
     1600         The field can contain multiple product tokens (<a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 3.4</a> of <a href="#Part1" id="rfc.xref.Part1.28"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and comments identifying the server and any significant subproducts. The product tokens are listed in order of their significance
    16011601         for identifying the application.
    16021602      </p>
     
    16191619      <p id="rfc.section.10.9.p.1">The request-header field "User-Agent" contains information about the user agent originating the request. This is for statistical
    16201620         purposes, the tracing of protocol violations, and automated recognition of user agents for the sake of tailoring responses
    1621          to avoid particular user agent limitations. User agents <em class="bcp14">SHOULD</em> include this field with requests. The field can contain multiple product tokens (<a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 3.5</a> of <a href="#Part1" id="rfc.xref.Part1.30"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and comments identifying the agent and any subproducts which form a significant part of the user agent. By convention, the
     1621         to avoid particular user agent limitations. User agents <em class="bcp14">SHOULD</em> include this field with requests. The field can contain multiple product tokens (<a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 3.4</a> of <a href="#Part1" id="rfc.xref.Part1.30"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and comments identifying the agent and any subproducts which form a significant part of the user agent. By convention, the
    16221622         product tokens are listed in order of their significance for identifying the application.
    16231623      </p>
     
    18991899               <tr>
    19001900                  <td>414</td>
    1901                   <td>Request-URI Too Long</td>
    1902                   <td> <a href="#status.414" id="rfc.xref.status.414.2" title="414 Request-URI Too Long">Section&nbsp;9.4.15</a>
     1901                  <td>Request-target Too Long</td>
     1902                  <td> <a href="#status.414" id="rfc.xref.status.414.2" title="414 Request-target Too Long">Section&nbsp;9.4.15</a>
    19031903                  </td>
    19041904               </tr>
     
    20822082      </p>
    20832083      <p id="rfc.section.12.2.p.3">Authors of services should not use GET-based forms for the submission of sensitive data because that data will be encoded
    2084          in the Request-URI. Many existing servers, proxies, and user agents log or display the Request-URI in places where it might
    2085          be visible to third parties. Such services can use POST-based form submission instead.
     2084         in the Request-target. Many existing servers, proxies, and user agents log or display the Request-target in places where it
     2085         might be visible to third parties. Such services can use POST-based form submission instead.
    20862086      </p>
    20872087      <h2 id="rfc.section.12.3"><a href="#rfc.section.12.3">12.3</a>&nbsp;<a id="location.spoofing" href="#location.spoofing">Location Headers and Spoofing</a></h2>
     
    24112411                  <li class="indline1">412 Precondition Failed (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.412.1">5</a>, <a class="iref" href="#rfc.iref.54"><b>9.4.13</b></a>, <a class="iref" href="#rfc.xref.status.412.2">11.2</a></li>
    24122412                  <li class="indline1">413 Request Entity Too Large (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.413.1">5</a>, <a class="iref" href="#rfc.iref.55"><b>9.4.14</b></a>, <a class="iref" href="#rfc.xref.status.413.2">11.2</a></li>
    2413                   <li class="indline1">414 Request-URI Too Long (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.414.1">5</a>, <a class="iref" href="#rfc.iref.56"><b>9.4.15</b></a>, <a class="iref" href="#rfc.xref.status.414.2">11.2</a></li>
     2413                  <li class="indline1">414 Request-target Too Long (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.414.1">5</a>, <a class="iref" href="#rfc.iref.56"><b>9.4.15</b></a>, <a class="iref" href="#rfc.xref.status.414.2">11.2</a></li>
    24142414                  <li class="indline1">415 Unsupported Media Type (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.415.1">5</a>, <a class="iref" href="#rfc.iref.57"><b>9.4.16</b></a>, <a class="iref" href="#rfc.xref.status.415.2">11.2</a></li>
    24152415                  <li class="indline1">416 Requested Range Not Satisfiable (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.416.1">5</a>, <a class="iref" href="#rfc.iref.58"><b>9.4.17</b></a>, <a class="iref" href="#rfc.xref.status.416.2">11.2</a></li>
     
    25342534            <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind">
    25352535                  <li class="indline1"><em>Part1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.1">1</a>, <a class="iref" href="#rfc.xref.Part1.2">2</a>, <a class="iref" href="#rfc.xref.Part1.3">2</a>, <a class="iref" href="#rfc.xref.Part1.4">2</a>, <a class="iref" href="#rfc.xref.Part1.5">2</a>, <a class="iref" href="#rfc.xref.Part1.6">2</a>, <a class="iref" href="#rfc.xref.Part1.7">2</a>, <a class="iref" href="#rfc.xref.Part1.8">2</a>, <a class="iref" href="#rfc.xref.Part1.9">2</a>, <a class="iref" href="#rfc.xref.Part1.10">2</a>, <a class="iref" href="#rfc.xref.Part1.11">2</a>, <a class="iref" href="#rfc.xref.Part1.12">2</a>, <a class="iref" href="#rfc.xref.Part1.13">2</a>, <a class="iref" href="#rfc.xref.Part1.14">2</a>, <a class="iref" href="#rfc.xref.Part1.15">2</a>, <a class="iref" href="#rfc.xref.Part1.16">2</a>, <a class="iref" href="#rfc.xref.Part1.17">2</a>, <a class="iref" href="#rfc.xref.Part1.18">2</a>, <a class="iref" href="#rfc.xref.Part1.19">2</a>, <a class="iref" href="#rfc.xref.Part1.20">4</a>, <a class="iref" href="#rfc.xref.Part1.21">4</a>, <a class="iref" href="#rfc.xref.Part1.22">7</a>, <a class="iref" href="#rfc.xref.Part1.23">8.8</a>, <a class="iref" href="#rfc.xref.Part1.24">8.8</a>, <a class="iref" href="#rfc.xref.Part1.25">9.1.1</a>, <a class="iref" href="#rfc.xref.Part1.26">9.5.6</a>, <a class="iref" href="#rfc.xref.Part1.27">10.2</a>, <a class="iref" href="#rfc.xref.Part1.28">10.8</a>, <a class="iref" href="#rfc.xref.Part1.29">10.8</a>, <a class="iref" href="#rfc.xref.Part1.30">10.9</a>, <a class="iref" href="#Part1"><b>14.1</b></a>, <a class="iref" href="#rfc.xref.Part1.31">A.2</a><ul class="ind">
    2536                         <li class="indline1"><em>Section 2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.2">2</a></li>
    2537                         <li class="indline1"><em>Section 2.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.3">2</a>, <a class="iref" href="#rfc.xref.Part1.4">2</a>, <a class="iref" href="#rfc.xref.Part1.5">2</a>, <a class="iref" href="#rfc.xref.Part1.6">2</a>, <a class="iref" href="#rfc.xref.Part1.7">2</a>, <a class="iref" href="#rfc.xref.Part1.8">2</a>, <a class="iref" href="#rfc.xref.Part1.9">2</a>, <a class="iref" href="#rfc.xref.Part1.10">2</a>, <a class="iref" href="#rfc.xref.Part1.11">2</a>, <a class="iref" href="#rfc.xref.Part1.12">2</a></li>
     2536                        <li class="indline1"><em>Section 1.2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.2">2</a></li>
     2537                        <li class="indline1"><em>Section 1.2.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.3">2</a>, <a class="iref" href="#rfc.xref.Part1.4">2</a>, <a class="iref" href="#rfc.xref.Part1.5">2</a>, <a class="iref" href="#rfc.xref.Part1.6">2</a>, <a class="iref" href="#rfc.xref.Part1.7">2</a>, <a class="iref" href="#rfc.xref.Part1.8">2</a>, <a class="iref" href="#rfc.xref.Part1.9">2</a>, <a class="iref" href="#rfc.xref.Part1.10">2</a>, <a class="iref" href="#rfc.xref.Part1.11">2</a>, <a class="iref" href="#rfc.xref.Part1.12">2</a></li>
     2538                        <li class="indline1"><em>Section 2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.13">2</a>, <a class="iref" href="#rfc.xref.Part1.14">2</a>, <a class="iref" href="#rfc.xref.Part1.15">2</a>, <a class="iref" href="#rfc.xref.Part1.17">2</a></li>
    25382539                        <li class="indline1"><em>Section 3.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.26">9.5.6</a></li>
    2539                         <li class="indline1"><em>Section 3.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.13">2</a>, <a class="iref" href="#rfc.xref.Part1.14">2</a>, <a class="iref" href="#rfc.xref.Part1.15">2</a>, <a class="iref" href="#rfc.xref.Part1.18">2</a></li>
    2540                         <li class="indline1"><em>Section 3.3.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.16">2</a></li>
    2541                         <li class="indline1"><em>Section 3.5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.17">2</a>, <a class="iref" href="#rfc.xref.Part1.28">10.8</a>, <a class="iref" href="#rfc.xref.Part1.30">10.9</a></li>
     2540                        <li class="indline1"><em>Section 3.2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.16">2</a></li>
     2541                        <li class="indline1"><em>Section 3.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.18">2</a>, <a class="iref" href="#rfc.xref.Part1.28">10.8</a>, <a class="iref" href="#rfc.xref.Part1.30">10.9</a></li>
    25422542                        <li class="indline1"><em>Section 4.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.22">7</a></li>
    25432543                        <li class="indline1"><em>Section 7.2.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.25">9.1.1</a>, <a class="iref" href="#rfc.xref.Part1.27">10.2</a></li>
     
    26492649                        <li class="indline1">412 Precondition Failed&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.412.1">5</a>, <a class="iref" href="#rfc.iref.s.31"><b>9.4.13</b></a>, <a class="iref" href="#rfc.xref.status.412.2">11.2</a></li>
    26502650                        <li class="indline1">413 Request Entity Too Large&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.413.1">5</a>, <a class="iref" href="#rfc.iref.s.32"><b>9.4.14</b></a>, <a class="iref" href="#rfc.xref.status.413.2">11.2</a></li>
    2651                         <li class="indline1">414 Request-URI Too Long&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.414.1">5</a>, <a class="iref" href="#rfc.iref.s.33"><b>9.4.15</b></a>, <a class="iref" href="#rfc.xref.status.414.2">11.2</a></li>
     2651                        <li class="indline1">414 Request-target Too Long&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.414.1">5</a>, <a class="iref" href="#rfc.iref.s.33"><b>9.4.15</b></a>, <a class="iref" href="#rfc.xref.status.414.2">11.2</a></li>
    26522652                        <li class="indline1">415 Unsupported Media Type&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.415.1">5</a>, <a class="iref" href="#rfc.iref.s.34"><b>9.4.16</b></a>, <a class="iref" href="#rfc.xref.status.415.2">11.2</a></li>
    26532653                        <li class="indline1">416 Requested Range Not Satisfiable&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.416.1">5</a>, <a class="iref" href="#rfc.iref.s.35"><b>9.4.17</b></a>, <a class="iref" href="#rfc.xref.status.416.2">11.2</a></li>
Note: See TracChangeset for help on using the changeset viewer.