Changeset 660


Ignore:
Timestamp:
30/07/09 11:30:31 (13 years ago)
Author:
fielding@…
Message:

editorial: move remaining terminology to part 3 for later edit.
update HTML

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

Legend:

Unmodified
Added
Removed

  • draft-ietf-httpbis/latest/p1-messaging.html

    r651 r660  
    367367      <link rel="Appendix" title="A Tolerant Applications" href="#rfc.section.A">
    368368      <link rel="Appendix" title="B Compatibility with Previous Versions" href="#rfc.section.B">
    369       <link rel="Appendix" title="C Terminology" href="#rfc.section.C">
    370       <link rel="Appendix" title="D Collected ABNF" href="#rfc.section.D">
    371       <link rel="Appendix" title="E Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.E">
     369      <link rel="Appendix" title="C Collected ABNF" href="#rfc.section.C">
     370      <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D">
    372371      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.439, 2009-06-09 18:43:39, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    373372      <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
    … …  
    466465         <tr>
    467466            <td class="header left"></td>
    468             <td class="header right">July 29, 2009</td>
     467            <td class="header right">July 30, 2009</td>
    469468         </tr>
    470469      </table>
    … …  
    508507         list is at &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/report/11">http://tools.ietf.org/wg/httpbis/trac/report/11</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>&gt;.
    509508      </p> 
    510       <p>The changes in this draft are summarized in <a href="#changes.since.07" title="Since draft-ietf-httpbis-p1-messaging-07">Appendix&nbsp;E.9</a>.
     509      <p>The changes in this draft are summarized in <a href="#changes.since.07" title="Since draft-ietf-httpbis-p1-messaging-07">Appendix&nbsp;D.9</a>.
    511510      </p>
    512511      <hr class="noprint">
    … …  
    653652            </ul>
    654653         </li>
    655          <li class="tocline0">C.&nbsp;&nbsp;&nbsp;<a href="#terminology">Terminology</a></li>
    656          <li class="tocline0">D.&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
    657          <li class="tocline0">E.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc">
    658                <li class="tocline1">E.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.1">Since RFC2616</a></li>
    659                <li class="tocline1">E.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.2">Since draft-ietf-httpbis-p1-messaging-00</a></li>
    660                <li class="tocline1">E.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.3">Since draft-ietf-httpbis-p1-messaging-01</a></li>
    661                <li class="tocline1">E.4&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p1-messaging-02</a></li>
    662                <li class="tocline1">E.5&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p1-messaging-03</a></li>
    663                <li class="tocline1">E.6&nbsp;&nbsp;&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p1-messaging-04</a></li>
    664                <li class="tocline1">E.7&nbsp;&nbsp;&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-p1-messaging-05</a></li>
    665                <li class="tocline1">E.8&nbsp;&nbsp;&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-p1-messaging-06</a></li>
    666                <li class="tocline1">E.9&nbsp;&nbsp;&nbsp;<a href="#changes.since.07">Since draft-ietf-httpbis-p1-messaging-07</a></li>
     654         <li class="tocline0">C.&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
     655         <li class="tocline0">D.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc">
     656               <li class="tocline1">D.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.1">Since RFC2616</a></li>
     657               <li class="tocline1">D.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.2">Since draft-ietf-httpbis-p1-messaging-00</a></li>
     658               <li class="tocline1">D.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.3">Since draft-ietf-httpbis-p1-messaging-01</a></li>
     659               <li class="tocline1">D.4&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p1-messaging-02</a></li>
     660               <li class="tocline1">D.5&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p1-messaging-03</a></li>
     661               <li class="tocline1">D.6&nbsp;&nbsp;&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p1-messaging-04</a></li>
     662               <li class="tocline1">D.7&nbsp;&nbsp;&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-p1-messaging-05</a></li>
     663               <li class="tocline1">D.8&nbsp;&nbsp;&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-p1-messaging-06</a></li>
     664               <li class="tocline1">D.9&nbsp;&nbsp;&nbsp;<a href="#changes.since.07">Since draft-ietf-httpbis-p1-messaging-07</a></li>
    667665            </ul>
    668666         </li>
    … …  
    673671         MIME-like message payloads for flexible interaction with network-based hypertext information systems. HTTP relies upon the
    674672         Uniform Resource Identifier (URI) standard <a href="#RFC3986" id="rfc.xref.RFC3986.1"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a> to indicate request targets and relationships between resources. Messages are passed in a format similar to that used by Internet
    675          mail <a href="#RFC5322" id="rfc.xref.RFC5322.1"><cite title="Internet Message Format">[RFC5322]</cite></a> and the Multipurpose Internet Mail Extensions (MIME) <a href="#RFC2045" id="rfc.xref.RFC2045.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a> (see <a href="p3-payload.html#differences.between.http.entities.and.rfc.2045.entities" title="Differences Between HTTP Entities and RFC 2045 Entities">Appendix A</a> of <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a> for the differences between HTTP and MIME messages).
     673         mail <a href="#RFC5322" id="rfc.xref.RFC5322.1"><cite title="Internet Message Format">[RFC5322]</cite></a> and the Multipurpose Internet Mail Extensions (MIME) <a href="#RFC2045" id="rfc.xref.RFC2045.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a> (see <a href="p3-payload.html#differences.between.http.entities.and.rfc.2045.entities" title="ERROR: Anchor 'differences.between.http.entities.and.rfc.2045.entities' not found in p3-payload.xml.">Appendix ERROR: Anchor 'differences.between.http.entities.and.rfc.2045.entities' not found in p3-payload.xml.</a> of <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a> for the differences between HTTP and MIME messages).
    676674      </p>
    677675      <p id="rfc.section.1.p.2">HTTP is a generic interface protocol for information systems. It is designed to hide the details of how a service is implemented
    … …  
    739737 
    740738  1#element =&gt; *( "," OWS ) element *( OWS "," [ OWS element ] )
    741 </pre><p id="rfc.section.1.2.1.p.8"> <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;D</a> shows the collected ABNF, with the list rules expanded as explained above.
     739</pre><p id="rfc.section.1.2.1.p.8"> <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;C</a> shows the collected ABNF, with the list rules expanded as explained above.
    742740      </p>
    743741      <h3 id="rfc.section.1.2.2"><a href="#rfc.section.1.2.2">1.2.2</a>&nbsp;<a id="basic.rules" href="#basic.rules">Basic Rules</a></h3>
    744742      <div id="rule.CRLF">
    745743         <p id="rfc.section.1.2.2.p.1">  HTTP/1.1 defines the sequence CR LF as the end-of-line marker for all protocol elements except the entity-body (see <a href="#tolerant.applications" title="Tolerant Applications">Appendix&nbsp;A</a> for tolerant applications). The end-of-line marker within an entity-body is defined by its associated media type, as described
    746             in <a href="p3-payload.html#media.types" title="Media Types">Section 2.3</a> of <a href="#Part3" id="rfc.xref.Part3.2"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>.
     744            in <a href="p3-payload.html#media.types" title="ERROR: Anchor 'media.types' not found in p3-payload.xml.">Appendix ERROR: Anchor 'media.types' not found in p3-payload.xml.</a> of <a href="#Part3" id="rfc.xref.Part3.2"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>.
    747745         </p>
    748746      </div>
    … …  
    797795      <div id="rfc.figure.u.9"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">request-header</a>  = &lt;request-header, defined in <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#request.header.fields" title="Request Header Fields">Section 3</a>&gt;
    798796  <a href="#abnf.dependencies" class="smpl">response-header</a> = &lt;response-header, defined in <a href="#Part2" id="rfc.xref.Part2.2"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#response.header.fields" title="Response Header Fields">Section 5</a>&gt;
    799 </pre><div id="rfc.figure.u.10"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">entity-body</a>     = &lt;entity-body, defined in <a href="#Part3" id="rfc.xref.Part3.3"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.body" title="Entity Body">Section 3.2</a>&gt;
    800   <a href="#abnf.dependencies" class="smpl">entity-header</a>   = &lt;entity-header, defined in <a href="#Part3" id="rfc.xref.Part3.4"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.header.fields" title="Entity Header Fields">Section 3.1</a>&gt;
     797</pre><div id="rfc.figure.u.10"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">entity-body</a>     = &lt;entity-body, defined in <a href="#Part3" id="rfc.xref.Part3.3"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.body" title="ERROR: Anchor 'entity.body' not found in p3-payload.xml.">Appendix ERROR: Anchor 'entity.body' not found in p3-payload.xml.</a>&gt;
     798  <a href="#abnf.dependencies" class="smpl">entity-header</a>   = &lt;entity-header, defined in <a href="#Part3" id="rfc.xref.Part3.4"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.header.fields" title="ERROR: Anchor 'entity.header.fields' not found in p3-payload.xml.">Appendix ERROR: Anchor 'entity.header.fields' not found in p3-payload.xml.</a>&gt;
    801799</pre><div id="rfc.figure.u.11"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">Cache-Control</a>   = &lt;Cache-Control, defined in <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.pragma" title="Pragma">Section 3.4</a>&gt;
    802800  <a href="#abnf.dependencies" class="smpl">Pragma</a>          = &lt;Pragma, defined in <a href="#Part6" id="rfc.xref.Part6.2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.pragma" title="Pragma">Section 3.4</a>&gt;
    … …  
    12231221                  *(( <a href="#general.header.fields" class="smpl">general-header</a>        ; <a href="#general.header.fields" title="General Header Fields">Section&nbsp;2.7.5</a>
    12241222                   / <a href="#abnf.dependencies" class="smpl">request-header</a>         ; <a href="#Part2" id="rfc.xref.Part2.3"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#request.header.fields" title="Request Header Fields">Section 3</a>
    1225                    / <a href="#abnf.dependencies" class="smpl">entity-header</a> ) <a href="#core.rules" class="smpl">CRLF</a> ) ; <a href="#Part3" id="rfc.xref.Part3.5"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.header.fields" title="Entity Header Fields">Section 3.1</a>
     1223                   / <a href="#abnf.dependencies" class="smpl">entity-header</a> ) <a href="#core.rules" class="smpl">CRLF</a> ) ; <a href="#Part3" id="rfc.xref.Part3.5"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.header.fields" title="ERROR: Anchor 'entity.header.fields' not found in p3-payload.xml.">Appendix ERROR: Anchor 'entity.header.fields' not found in p3-payload.xml.</a>
    12261224                  <a href="#core.rules" class="smpl">CRLF</a>
    12271225                  [ <a href="#message.body" class="smpl">message-body</a> ]          ; <a href="#message.body" title="Message Body">Section&nbsp;2.7.3</a>
    … …  
    13151313                  *(( <a href="#general.header.fields" class="smpl">general-header</a>        ; <a href="#general.header.fields" title="General Header Fields">Section&nbsp;2.7.5</a>
    13161314                   / <a href="#abnf.dependencies" class="smpl">response-header</a>        ; <a href="#Part2" id="rfc.xref.Part2.6"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#response.header.fields" title="Response Header Fields">Section 5</a>
    1317                    / <a href="#abnf.dependencies" class="smpl">entity-header</a> ) <a href="#core.rules" class="smpl">CRLF</a> )  ; <a href="#Part3" id="rfc.xref.Part3.6"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.header.fields" title="Entity Header Fields">Section 3.1</a>
     1315                   / <a href="#abnf.dependencies" class="smpl">entity-header</a> ) <a href="#core.rules" class="smpl">CRLF</a> )  ; <a href="#Part3" id="rfc.xref.Part3.6"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.header.fields" title="ERROR: Anchor 'entity.header.fields' not found in p3-payload.xml.">Appendix ERROR: Anchor 'entity.header.fields' not found in p3-payload.xml.</a>
    13181316                  <a href="#core.rules" class="smpl">CRLF</a>
    13191317                  [ <a href="#message.body" class="smpl">message-body</a> ]          ; <a href="#message.body" title="Message Body">Section&nbsp;2.7.3</a>
    … …  
    14491447      </p>
    14501448      <p id="rfc.section.2.10.2.p.8">The Internet Assigned Numbers Authority (IANA) acts as a registry for transfer-coding value tokens. Initially, the registry
    1451          contains the following tokens: "chunked" (<a href="#chunked.transfer.encoding" title="Chunked Transfer Coding">Section&nbsp;2.10.2.1</a>), "gzip", "compress", and "deflate" (<a href="p3-payload.html#content.codings" title="Content Codings">Section 2.2</a> of <a href="#Part3" id="rfc.xref.Part3.7"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>).
    1452       </p>
    1453       <p id="rfc.section.2.10.2.p.9">New transfer-coding value tokens <em class="bcp14">SHOULD</em> be registered in the same way as new content-coding value tokens (<a href="p3-payload.html#content.codings" title="Content Codings">Section 2.2</a> of <a href="#Part3" id="rfc.xref.Part3.8"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>).
     1449         contains the following tokens: "chunked" (<a href="#chunked.transfer.encoding" title="Chunked Transfer Coding">Section&nbsp;2.10.2.1</a>), "gzip", "compress", and "deflate" (<a href="p3-payload.html#content.codings" title="ERROR: Anchor 'content.codings' not found in p3-payload.xml.">Appendix ERROR: Anchor 'content.codings' not found in p3-payload.xml.</a> of <a href="#Part3" id="rfc.xref.Part3.7"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>).
     1450      </p>
     1451      <p id="rfc.section.2.10.2.p.9">New transfer-coding value tokens <em class="bcp14">SHOULD</em> be registered in the same way as new content-coding value tokens (<a href="p3-payload.html#content.codings" title="ERROR: Anchor 'content.codings' not found in p3-payload.xml.">Appendix ERROR: Anchor 'content.codings' not found in p3-payload.xml.</a> of <a href="#Part3" id="rfc.xref.Part3.8"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>).
    14541452      </p>
    14551453      <p id="rfc.section.2.10.2.p.10">A server which receives an entity-body with a transfer-coding it does not understand <em class="bcp14">SHOULD</em> return 501 (Not Implemented), and close the connection. A server <em class="bcp14">MUST NOT</em> send transfer-codings to an HTTP/1.0 client.
    … …  
    15281526      </p>
    15291527      <h3 id="rfc.section.2.10.4"><a href="#rfc.section.2.10.4">2.10.4</a>&nbsp;<a id="quality.values" href="#quality.values">Quality Values</a></h3>
    1530       <p id="rfc.section.2.10.4.p.1">Both transfer codings (TE request header, <a href="#header.te" id="rfc.xref.header.te.3" title="TE">Section&nbsp;3.5</a>) and content negotiation (<a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 4</a> of <a href="#Part3" id="rfc.xref.Part3.9"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) use short "floating point" numbers to indicate the relative importance ("weight") of various negotiable parameters. A weight
     1528      <p id="rfc.section.2.10.4.p.1">Both transfer codings (TE request header, <a href="#header.te" id="rfc.xref.header.te.3" title="TE">Section&nbsp;3.5</a>) and content negotiation (<a href="p3-payload.html#content.negotiation" title="ERROR: Anchor 'content.negotiation' not found in p3-payload.xml.">Appendix ERROR: Anchor 'content.negotiation' not found in p3-payload.xml.</a> of <a href="#Part3" id="rfc.xref.Part3.9"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) use short "floating point" numbers to indicate the relative importance ("weight") of various negotiable parameters. A weight
    15311529         is normalized to a real number in the range 0 through 1, where 0 is the minimum and 1 the maximum value. If a parameter has
    15321530         a quality value of 0, then content with this parameter is `not acceptable' for the client. HTTP/1.1 applications <em class="bcp14">MUST NOT</em> generate more than three digits after the decimal point. User configuration of these values <em class="bcp14">SHOULD</em> also be limited in this fashion.
    … …  
    26332631      <p id="rfc.section.B.4.p.8">Clarify exactly when close connection options must be sent. (<a href="#header.connection" id="rfc.xref.header.connection.8" title="Connection">Section&nbsp;3.1</a>)
    26342632      </p>
    2635       <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="terminology" href="#terminology">Terminology</a></h1>
    2636       <p id="rfc.section.C.p.1">This specification uses a number of terms to refer to the roles played by participants in, and objects of, the HTTP communication.</p>
    2637       <p id="rfc.section.C.p.2"> <span id="rfc.iref.c.7"></span>  <dfn>content negotiation</dfn> 
    2638       </p>
    2639       <dl class="empty">
    2640          <dd>The mechanism for selecting the appropriate representation when servicing a request, as described in <a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 4</a> of <a href="#Part3" id="rfc.xref.Part3.12"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. The representation of entities in any response can be negotiated (including error responses).
    2641          </dd>
    2642       </dl>
    2643       <p id="rfc.section.C.p.3"> <span id="rfc.iref.e.1"></span>  <dfn>entity</dfn> 
    2644       </p>
    2645       <dl class="empty">
    2646          <dd>The information transferred as the payload of a request or response. An entity consists of metadata in the form of entity-header
    2647             fields and content in the form of an entity-body, as described in <a href="p3-payload.html#entity" title="Entity">Section 3</a> of <a href="#Part3" id="rfc.xref.Part3.13"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>.
    2648          </dd>
    2649       </dl>
    2650       <p id="rfc.section.C.p.4"> <span id="rfc.iref.r.5"></span>  <dfn>representation</dfn> 
    2651       </p>
    2652       <dl class="empty">
    2653          <dd>An entity included with a response that is subject to content negotiation, as described in <a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 4</a> of <a href="#Part3" id="rfc.xref.Part3.14"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. There may exist multiple representations associated with a particular response status.
    2654          </dd>
    2655       </dl>
    2656       <p id="rfc.section.C.p.5"> <span id="rfc.iref.v.2"></span>  <dfn>variant</dfn> 
    2657       </p>
    2658       <dl class="empty">
    2659          <dd>A resource may have one, or more than one, representation(s) associated with it at any given instant. Each of these representations
    2660             is termed a `variant'. Use of the term `variant' does not necessarily imply that the resource is subject to content negotiation.
    2661          </dd>
    2662       </dl>
    2663       <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
     2633      <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
    26642634      <div id="rfc.figure.u.71"></div> <pre class="inline"><a href="#rule.whitespace" class="smpl">BWS</a> = OWS
    26652635
    … …  
    28582828; https-URI defined but not used
    28592829; partial-URI defined but not used
    2860 </pre><h1 id="rfc.section.E"><a href="#rfc.section.E">E.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
    2861       <h2 id="rfc.section.E.1"><a href="#rfc.section.E.1">E.1</a>&nbsp;Since RFC2616
     2830</pre><h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
     2831      <h2 id="rfc.section.D.1"><a href="#rfc.section.D.1">D.1</a>&nbsp;Since RFC2616
    28622832      </h2>
    2863       <p id="rfc.section.E.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
    2864       </p>
    2865       <h2 id="rfc.section.E.2"><a href="#rfc.section.E.2">E.2</a>&nbsp;Since draft-ietf-httpbis-p1-messaging-00
     2833      <p id="rfc.section.D.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
     2834      </p>
     2835      <h2 id="rfc.section.D.2"><a href="#rfc.section.D.2">D.2</a>&nbsp;Since draft-ietf-httpbis-p1-messaging-00
    28662836      </h2>
    2867       <p id="rfc.section.E.2.p.1">Closed issues: </p>
     2837      <p id="rfc.section.D.2.p.1">Closed issues: </p>
    28682838      <ul>
    28692839         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/1">http://tools.ietf.org/wg/httpbis/trac/ticket/1</a>&gt;: "HTTP Version should be case sensitive" (&lt;<a href="http://purl.org/NET/http-errata#verscase">http://purl.org/NET/http-errata#verscase</a>&gt;)
    … …  
    29062876         </li>
    29072877      </ul>
    2908       <p id="rfc.section.E.2.p.2">Other changes: </p>
     2878      <p id="rfc.section.D.2.p.2">Other changes: </p>
    29092879      <ul>
    29102880         <li>Update media type registrations to use RFC4288 template.</li>
    … …  
    29122882         </li>
    29132883      </ul>
    2914       <h2 id="rfc.section.E.3"><a href="#rfc.section.E.3">E.3</a>&nbsp;Since draft-ietf-httpbis-p1-messaging-01
     2884      <h2 id="rfc.section.D.3"><a href="#rfc.section.D.3">D.3</a>&nbsp;Since draft-ietf-httpbis-p1-messaging-01
    29152885      </h2>
    2916       <p id="rfc.section.E.3.p.1">Closed issues: </p>
     2886      <p id="rfc.section.D.3.p.1">Closed issues: </p>
    29172887      <ul>
    29182888         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/19">http://tools.ietf.org/wg/httpbis/trac/ticket/19</a>&gt;: "Bodies on GET (and other) requests"
    … …  
    29252895         </li>
    29262896      </ul>
    2927       <p id="rfc.section.E.3.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
     2897      <p id="rfc.section.D.3.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
    29282898      </p>
    29292899      <ul>
    … …  
    29402910         <li>Rewrite prose rule "token" in terms of "tchar", rewrite prose rule "TEXT".</li>
    29412911      </ul>
    2942       <h2 id="rfc.section.E.4"><a href="#rfc.section.E.4">E.4</a>&nbsp;<a id="changes.since.02" href="#changes.since.02">Since draft-ietf-httpbis-p1-messaging-02</a></h2>
    2943       <p id="rfc.section.E.4.p.1">Closed issues: </p>
     2912      <h2 id="rfc.section.D.4"><a href="#rfc.section.D.4">D.4</a>&nbsp;<a id="changes.since.02" href="#changes.since.02">Since draft-ietf-httpbis-p1-messaging-02</a></h2>
     2913      <p id="rfc.section.D.4.p.1">Closed issues: </p>
    29442914      <ul>
    29452915         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/51">http://tools.ietf.org/wg/httpbis/trac/ticket/51</a>&gt;: "HTTP-date vs. rfc1123-date"
    … …  
    29482918         </li>
    29492919      </ul>
    2950       <p id="rfc.section.E.4.p.2">Ongoing work on IANA Message Header Registration (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>&gt;):
     2920      <p id="rfc.section.D.4.p.2">Ongoing work on IANA Message Header Registration (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>&gt;):
    29512921      </p>
    29522922      <ul>
    29532923         <li>Reference RFC 3984, and update header registrations for headers defined in this document.</li>
    29542924      </ul>
    2955       <p id="rfc.section.E.4.p.3">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
     2925      <p id="rfc.section.D.4.p.3">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
    29562926      </p>
    29572927      <ul>
    29582928         <li>Replace string literals when the string really is case-sensitive (HTTP-Version).</li>
    29592929      </ul>
    2960       <h2 id="rfc.section.E.5"><a href="#rfc.section.E.5">E.5</a>&nbsp;<a id="changes.since.03" href="#changes.since.03">Since draft-ietf-httpbis-p1-messaging-03</a></h2>
    2961       <p id="rfc.section.E.5.p.1">Closed issues: </p>
     2930      <h2 id="rfc.section.D.5"><a href="#rfc.section.D.5">D.5</a>&nbsp;<a id="changes.since.03" href="#changes.since.03">Since draft-ietf-httpbis-p1-messaging-03</a></h2>
     2931      <p id="rfc.section.D.5.p.1">Closed issues: </p>
    29622932      <ul>
    29632933         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/28">http://tools.ietf.org/wg/httpbis/trac/ticket/28</a>&gt;: "Connection closing"
    … …  
    29742944         </li>
    29752945      </ul>
    2976       <p id="rfc.section.E.5.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
     2946      <p id="rfc.section.D.5.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
    29772947      </p>
    29782948      <ul>
    … …  
    29802950         <li>Replace HEX by HEXDIG for future consistence with RFC 5234's core rules.</li>
    29812951      </ul>
    2982       <h2 id="rfc.section.E.6"><a href="#rfc.section.E.6">E.6</a>&nbsp;<a id="changes.since.04" href="#changes.since.04">Since draft-ietf-httpbis-p1-messaging-04</a></h2>
    2983       <p id="rfc.section.E.6.p.1">Closed issues: </p>
     2952      <h2 id="rfc.section.D.6"><a href="#rfc.section.D.6">D.6</a>&nbsp;<a id="changes.since.04" href="#changes.since.04">Since draft-ietf-httpbis-p1-messaging-04</a></h2>
     2953      <p id="rfc.section.D.6.p.1">Closed issues: </p>
    29842954      <ul>
    29852955         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/34">http://tools.ietf.org/wg/httpbis/trac/ticket/34</a>&gt;: "Out-of-date reference for URIs"
    … …  
    29882958         </li>
    29892959      </ul>
    2990       <p id="rfc.section.E.6.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
     2960      <p id="rfc.section.D.6.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
    29912961      </p>
    29922962      <ul>
    … …  
    29972967         <li>Rewrite ABNFs to spell out whitespace rules, factor out header value format definitions.</li>
    29982968      </ul>
    2999       <h2 id="rfc.section.E.7"><a href="#rfc.section.E.7">E.7</a>&nbsp;<a id="changes.since.05" href="#changes.since.05">Since draft-ietf-httpbis-p1-messaging-05</a></h2>
    3000       <p id="rfc.section.E.7.p.1">Closed issues: </p>
     2969      <h2 id="rfc.section.D.7"><a href="#rfc.section.D.7">D.7</a>&nbsp;<a id="changes.since.05" href="#changes.since.05">Since draft-ietf-httpbis-p1-messaging-05</a></h2>
     2970      <p id="rfc.section.D.7.p.1">Closed issues: </p>
    30012971      <ul>
    30022972         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/30">http://tools.ietf.org/wg/httpbis/trac/ticket/30</a>&gt;: "Header LWS"
    … …  
    30212991         </li>
    30222992      </ul>
    3023       <p id="rfc.section.E.7.p.2">Final work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
     2993      <p id="rfc.section.D.7.p.2">Final work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
    30242994      </p>
    30252995      <ul>
    … …  
    30272997         <li>Add appendix containing collected and expanded ABNF.</li>
    30282998      </ul>
    3029       <p id="rfc.section.E.7.p.3">Other changes: </p>
     2999      <p id="rfc.section.D.7.p.3">Other changes: </p>
    30303000      <ul>
    30313001         <li>Rewrite introduction; add mostly new Architecture Section.</li>
    … …  
    30343004         </li>
    30353005      </ul>
    3036       <h2 id="rfc.section.E.8"><a href="#rfc.section.E.8">E.8</a>&nbsp;<a id="changes.since.06" href="#changes.since.06">Since draft-ietf-httpbis-p1-messaging-06</a></h2>
    3037       <p id="rfc.section.E.8.p.1">Closed issues: </p>
     3006      <h2 id="rfc.section.D.8"><a href="#rfc.section.D.8">D.8</a>&nbsp;<a id="changes.since.06" href="#changes.since.06">Since draft-ietf-httpbis-p1-messaging-06</a></h2>
     3007      <p id="rfc.section.D.8.p.1">Closed issues: </p>
    30383008      <ul>
    30393009         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/161">http://tools.ietf.org/wg/httpbis/trac/ticket/161</a>&gt;: "base for numeric protocol elements"
    … …  
    30423012         </li>
    30433013      </ul>
    3044       <p id="rfc.section.E.8.p.2">Partly resolved issues: </p>
     3014      <p id="rfc.section.D.8.p.2">Partly resolved issues: </p>
    30453015      <ul>
    30463016         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/88">http://tools.ietf.org/wg/httpbis/trac/ticket/88</a>&gt;: "205 Bodies" (took out language that implied that there may be methods for which a request body MUST NOT be included)
    … …  
    30493019         </li>
    30503020      </ul>
    3051       <h2 id="rfc.section.E.9"><a href="#rfc.section.E.9">E.9</a>&nbsp;<a id="changes.since.07" href="#changes.since.07">Since draft-ietf-httpbis-p1-messaging-07</a></h2>
    3052       <p id="rfc.section.E.9.p.1">Closed issues: </p>
     3021      <h2 id="rfc.section.D.9"><a href="#rfc.section.D.9">D.9</a>&nbsp;<a id="changes.since.07" href="#changes.since.07">Since draft-ietf-httpbis-p1-messaging-07</a></h2>
     3022      <p id="rfc.section.D.9.p.1">Closed issues: </p>
    30533023      <ul>
    30543024         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/157">http://tools.ietf.org/wg/httpbis/trac/ticket/157</a>&gt;: "IP addresses in URLs"
    30553025         </li>
    30563026      </ul>
    3057       <p id="rfc.section.E.9.p.2">Partly resolved issues: </p>
     3027      <p id="rfc.section.D.9.p.2">Partly resolved issues: </p>
    30583028      <ul>
    30593029         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/148">http://tools.ietf.org/wg/httpbis/trac/ticket/148</a>&gt;: "update IANA requirements wrt Transfer-Coding values" (add the IANA Considerations subsection)
    … …  
    30613031      </ul>
    30623032      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
    3063       <p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.K">K</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.N">N</a> <a href="#rfc.index.O">O</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.T">T</a> <a href="#rfc.index.U">U</a> <a href="#rfc.index.V">V</a>
     3033      <p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.K">K</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.N">N</a> <a href="#rfc.index.O">O</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.T">T</a> <a href="#rfc.index.U">U</a> <a href="#rfc.index.V">V</a>
    30643034      </p>
    30653035      <div class="print2col">
    … …  
    30753045                  <li class="indline1">connection&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.2">2.1</a></li>
    30763046                  <li class="indline1">Connection header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.connection.1">2.7.5</a>, <a class="iref" href="#rfc.xref.header.connection.2">2.11.1.2</a>, <a class="iref" href="#rfc.xref.header.connection.3">2.11.1.3</a>, <a class="iref" href="#rfc.iref.c.5"><b>3.1</b></a>, <a class="iref" href="#rfc.xref.header.connection.4">3.5</a>, <a class="iref" href="#rfc.xref.header.connection.5">3.8</a>, <a class="iref" href="#rfc.xref.header.connection.6">4.1</a>, <a class="iref" href="#rfc.xref.header.connection.7">B.2</a>, <a class="iref" href="#rfc.xref.header.connection.8">B.4</a></li>
    3077                   <li class="indline1">content negotiation&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.7">C</a></li>
    30783047                  <li class="indline1">Content-Length header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-length.1">2.7.4</a>, <a class="iref" href="#rfc.iref.c.6"><b>3.2</b></a>, <a class="iref" href="#rfc.xref.header.content-length.2">4.1</a>, <a class="iref" href="#rfc.xref.header.content-length.3">B.3</a></li>
    30793048               </ul>
    … …  
    30823051                  <li class="indline1">Date header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.date.1">2.7.5</a>, <a class="iref" href="#rfc.iref.d.2"><b>3.3</b></a>, <a class="iref" href="#rfc.xref.header.date.2">4.1</a></li>
    30833052                  <li class="indline1">downstream&nbsp;&nbsp;<a class="iref" href="#rfc.iref.d.1">2.2</a></li>
    3084                </ul>
    3085             </li>
    3086             <li class="indline0"><a id="rfc.index.E" href="#rfc.index.E"><b>E</b></a><ul class="ind">
    3087                   <li class="indline1">entity&nbsp;&nbsp;<a class="iref" href="#rfc.iref.e.1">C</a></li>
    30883053               </ul>
    30893054            </li>
    … …  
    32753240                     </ul>
    32763241                  </li>
    3277                   <li class="indline1"><em>Part3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.1">1</a>, <a class="iref" href="#rfc.xref.Part3.2">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.3">1.2.3</a>, <a class="iref" href="#rfc.xref.Part3.4">1.2.3</a>, <a class="iref" href="#rfc.xref.Part3.5">2.8</a>, <a class="iref" href="#rfc.xref.Part3.6">2.9</a>, <a class="iref" href="#rfc.xref.Part3.7">2.10.2</a>, <a class="iref" href="#rfc.xref.Part3.8">2.10.2</a>, <a class="iref" href="#rfc.xref.Part3.9">2.10.4</a>, <a class="iref" href="#Part3"><b>7.1</b></a>, <a class="iref" href="#rfc.xref.Part3.10">A</a>, <a class="iref" href="#rfc.xref.Part3.11">B.3</a>, <a class="iref" href="#rfc.xref.Part3.12">C</a>, <a class="iref" href="#rfc.xref.Part3.13">C</a>, <a class="iref" href="#rfc.xref.Part3.14">C</a><ul class="ind">
    3278                         <li class="indline1"><em>Section 2.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.7">2.10.2</a>, <a class="iref" href="#rfc.xref.Part3.8">2.10.2</a></li>
    3279                         <li class="indline1"><em>Section 2.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.2">1.2.2</a></li>
    3280                         <li class="indline1"><em>Section 3.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.4">1.2.3</a>, <a class="iref" href="#rfc.xref.Part3.5">2.8</a>, <a class="iref" href="#rfc.xref.Part3.6">2.9</a></li>
    3281                         <li class="indline1"><em>Section 3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.13">C</a></li>
    3282                         <li class="indline1"><em>Section 3.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.3">1.2.3</a></li>
    3283                         <li class="indline1"><em>Section 4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.9">2.10.4</a>, <a class="iref" href="#rfc.xref.Part3.12">C</a>, <a class="iref" href="#rfc.xref.Part3.14">C</a></li>
    3284                         <li class="indline1"><em>Appendix A</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.1">1</a></li>
     3242                  <li class="indline1"><em>Part3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.1">1</a>, <a class="iref" href="#rfc.xref.Part3.2">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.3">1.2.3</a>, <a class="iref" href="#rfc.xref.Part3.4">1.2.3</a>, <a class="iref" href="#rfc.xref.Part3.5">2.8</a>, <a class="iref" href="#rfc.xref.Part3.6">2.9</a>, <a class="iref" href="#rfc.xref.Part3.7">2.10.2</a>, <a class="iref" href="#rfc.xref.Part3.8">2.10.2</a>, <a class="iref" href="#rfc.xref.Part3.9">2.10.4</a>, <a class="iref" href="#Part3"><b>7.1</b></a>, <a class="iref" href="#rfc.xref.Part3.10">A</a>, <a class="iref" href="#rfc.xref.Part3.11">B.3</a><ul class="ind">
     3243                        <li class="indline1"><em>Appendix </em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.1">1</a></li>
     3244                        <li class="indline1"><em>Appendix </em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.2">1.2.2</a></li>
     3245                        <li class="indline1"><em>Appendix </em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.3">1.2.3</a></li>
     3246                        <li class="indline1"><em>Appendix </em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.4">1.2.3</a>, <a class="iref" href="#rfc.xref.Part3.5">2.8</a>, <a class="iref" href="#rfc.xref.Part3.6">2.9</a></li>
     3247                        <li class="indline1"><em>Appendix </em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.7">2.10.2</a>, <a class="iref" href="#rfc.xref.Part3.8">2.10.2</a></li>
     3248                        <li class="indline1"><em>Appendix </em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.9">2.10.4</a></li>
    32853249                     </ul>
    32863250                  </li>
    … …  
    32973261            </li>
    32983262            <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind">
    3299                   <li class="indline1">representation&nbsp;&nbsp;<a class="iref" href="#rfc.iref.r.5">C</a></li>
    33003263                  <li class="indline1">request&nbsp;&nbsp;<a class="iref" href="#rfc.iref.r.1">2.1</a></li>
    33013264                  <li class="indline1">resource&nbsp;&nbsp;<a class="iref" href="#rfc.iref.r.4"><b>2.6</b></a></li>
    … …  
    33183281                  <li class="indline1"><em>RFC2119</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>7.1</b></a>, <a class="iref" href="#rfc.xref.RFC2119.2">B.3</a></li>
    33193282                  <li class="indline1"><em>RFC2145</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2145.1">2.5</a>, <a class="iref" href="#rfc.xref.RFC2145.2">2.5</a>, <a class="iref" href="#RFC2145"><b>7.2</b></a>, <a class="iref" href="#rfc.xref.RFC2145.3">B.3</a></li>
    3320                   <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#rfc.xref.RFC2616.2">6</a>, <a class="iref" href="#RFC2616"><b>7.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.3">E.1</a></li>
     3283                  <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#rfc.xref.RFC2616.2">6</a>, <a class="iref" href="#RFC2616"><b>7.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.3">D.1</a></li>
    33213284                  <li class="indline1"><em>RFC2818</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2818.1">2.6.2</a>, <a class="iref" href="#RFC2818"><b>7.2</b></a></li>
    33223285                  <li class="indline1"><em>RFC2965</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2965.1">2.7.2</a>, <a class="iref" href="#RFC2965"><b>7.2</b></a></li>
    … …  
    33773340            </li>
    33783341            <li class="indline0"><a id="rfc.index.V" href="#rfc.index.V"><b>V</b></a><ul class="ind">
    3379                   <li class="indline1">variant&nbsp;&nbsp;<a class="iref" href="#rfc.iref.v.2">C</a></li>
    33803342                  <li class="indline1">Via header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.via.1">2.7.5</a>, <a class="iref" href="#rfc.iref.v.1"><b>3.9</b></a>, <a class="iref" href="#rfc.xref.header.via.2">4.1</a></li>
    33813343               </ul>

  • draft-ietf-httpbis/latest/p1-messaging.xml

    r651 r660  
    43624362</section>
    43634363
    4364 <section title="Terminology" anchor="terminology">
    4365 <t>
    4366    This specification uses a number of terms to refer to the roles
    4367    played by participants in, and objects of, the HTTP communication.
    4368 </t>
    4369 <t>
    4370   <iref item="content negotiation"/>
    4371   <x:dfn>content negotiation</x:dfn>
    4372   <list>
    4373     <t>
    4374       The mechanism for selecting the appropriate representation when
    4375       servicing a request, as described in &content.negotiation;. The
    4376       representation of entities in any response can be negotiated
    4377       (including error responses).
    4378     </t>
    4379   </list>
    4380 </t>
    4381 <t>
    4382   <iref item="entity"/>
    4383   <x:dfn>entity</x:dfn>
    4384   <list>
    4385     <t>
    4386       The information transferred as the payload of a request or
    4387       response. An entity consists of metadata in the form of
    4388       entity-header fields and content in the form of an entity-body, as
    4389       described in &entity;.
    4390     </t>
    4391   </list>
    4392 </t>
    4393 <t>
    4394   <iref item="representation"/>
    4395   <x:dfn>representation</x:dfn>
    4396   <list>
    4397     <t>
    4398       An entity included with a response that is subject to content
    4399       negotiation, as described in &content.negotiation;. There may exist multiple
    4400       representations associated with a particular response status.
    4401     </t>
    4402   </list>
    4403 </t>
    4404 <t>
    4405   <iref item="variant"/>
    4406   <x:dfn>variant</x:dfn>
    4407   <list>
    4408     <t>
    4409       A resource may have one, or more than one, representation(s)
    4410       associated with it at any given instant. Each of these
    4411       representations is termed a `variant'.  Use of the term `variant'
    4412       does not necessarily imply that the resource is subject to content
    4413       negotiation.
    4414     </t>
    4415   </list>
    4416 </t>
    4417 </section>
    4418 
    44194364<section xmlns:x="http://purl.org/net/xml2rfc/ext" title="Collected ABNF" anchor="collected.abnf">
    44204365<figure>

  • draft-ietf-httpbis/latest/p2-semantics.html

    r653 r660  
    471471         <tr>
    472472            <td class="header left"></td>
    473             <td class="header right">July 29, 2009</td>
     473            <td class="header right">July 30, 2009</td>
    474474         </tr>
    475475      </table>
    … …  
    706706  <a href="#abnf.dependencies" class="smpl">TE</a>            = &lt;TE, 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#header.upgrade" title="Upgrade">Section 3.8</a>&gt;
    707707  <a href="#abnf.dependencies" class="smpl">URI</a>           = &lt;URI, 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#uri" title="Uniform Resource Identifiers">Section 2.6</a>&gt;
    708 </pre><div id="rfc.figure.u.3"></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 5.1</a>&gt;
     708</pre><div id="rfc.figure.u.3"></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="ERROR: Anchor 'header.accept' not found in p3-payload.xml.">Appendix ERROR: Anchor 'header.accept' not found in p3-payload.xml.</a>&gt;
    709709  <a href="#abnf.dependencies" class="smpl">Accept-Charset</a> =
    710              &lt;Accept-Charset, defined in <a href="#Part3" id="rfc.xref.Part3.2"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-charset" title="Accept-Charset">Section 5.2</a>&gt;
     710             &lt;Accept-Charset, defined in <a href="#Part3" id="rfc.xref.Part3.2"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-charset" title="ERROR: Anchor 'header.accept-charset' not found in p3-payload.xml.">Appendix ERROR: Anchor 'header.accept-charset' not found in p3-payload.xml.</a>&gt;
    711711  <a href="#abnf.dependencies" class="smpl">Accept-Encoding</a> =
    712              &lt;Accept-Encoding, defined in <a href="#Part3" id="rfc.xref.Part3.3"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-encoding" title="Accept-Encoding">Section 5.3</a>&gt;
     712             &lt;Accept-Encoding, defined in <a href="#Part3" id="rfc.xref.Part3.3"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-encoding" title="ERROR: Anchor 'header.accept-encoding' not found in p3-payload.xml.">Appendix ERROR: Anchor 'header.accept-encoding' not found in p3-payload.xml.</a>&gt;
    713713  <a href="#abnf.dependencies" class="smpl">Accept-Language</a> =
    714              &lt;Accept-Language, defined in <a href="#Part3" id="rfc.xref.Part3.4"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-language" title="Accept-Language">Section 5.4</a>&gt;
     714             &lt;Accept-Language, defined in <a href="#Part3" id="rfc.xref.Part3.4"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-language" title="ERROR: Anchor 'header.accept-language' not found in p3-payload.xml.">Appendix ERROR: Anchor 'header.accept-language' not found in p3-payload.xml.</a>&gt;
    715715</pre><div id="rfc.figure.u.4"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">ETag</a>          = &lt;ETag, defined in <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.etag" title="ETag">Section 6.1</a>&gt;
    716716  <a href="#abnf.dependencies" class="smpl">If-Match</a>      = &lt;If-Match, defined in <a href="#Part4" id="rfc.xref.Part4.2"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-match" title="If-Match">Section 6.2</a>&gt;
    … …  
    769769         method invocation.
    770770      </p>
    771       <div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.3"></span>  <a href="#request.header.fields" class="smpl">request-header</a> = <a href="#abnf.dependencies" class="smpl">Accept</a>                   ; <a href="#Part3" id="rfc.xref.Part3.5"><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 5.1</a>
    772                  / <a href="#abnf.dependencies" class="smpl">Accept-Charset</a>           ; <a href="#Part3" id="rfc.xref.Part3.6"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-charset" title="Accept-Charset">Section 5.2</a>
    773                  / <a href="#abnf.dependencies" class="smpl">Accept-Encoding</a>          ; <a href="#Part3" id="rfc.xref.Part3.7"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-encoding" title="Accept-Encoding">Section 5.3</a>
    774                  / <a href="#abnf.dependencies" class="smpl">Accept-Language</a>          ; <a href="#Part3" id="rfc.xref.Part3.8"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-language" title="Accept-Language">Section 5.4</a>
     771      <div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.3"></span>  <a href="#request.header.fields" class="smpl">request-header</a> = <a href="#abnf.dependencies" class="smpl">Accept</a>                   ; <a href="#Part3" id="rfc.xref.Part3.5"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept" title="ERROR: Anchor 'header.accept' not found in p3-payload.xml.">Appendix ERROR: Anchor 'header.accept' not found in p3-payload.xml.</a>
     772                 / <a href="#abnf.dependencies" class="smpl">Accept-Charset</a>           ; <a href="#Part3" id="rfc.xref.Part3.6"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-charset" title="ERROR: Anchor 'header.accept-charset' not found in p3-payload.xml.">Appendix ERROR: Anchor 'header.accept-charset' not found in p3-payload.xml.</a>
     773                 / <a href="#abnf.dependencies" class="smpl">Accept-Encoding</a>          ; <a href="#Part3" id="rfc.xref.Part3.7"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-encoding" title="ERROR: Anchor 'header.accept-encoding' not found in p3-payload.xml.">Appendix ERROR: Anchor 'header.accept-encoding' not found in p3-payload.xml.</a>
     774                 / <a href="#abnf.dependencies" class="smpl">Accept-Language</a>          ; <a href="#Part3" id="rfc.xref.Part3.8"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-language" title="ERROR: Anchor 'header.accept-language' not found in p3-payload.xml.">Appendix ERROR: Anchor 'header.accept-language' not found in p3-payload.xml.</a>
    775775                 / <a href="#abnf.dependencies" class="smpl">Authorization</a>            ; <a href="#Part7" id="rfc.xref.Part7.5"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.authorization" title="Authorization">Section 3.1</a>
    776776                 / <a href="#header.expect" class="smpl">Expect</a>                   ; <a href="#header.expect" id="rfc.xref.header.expect.1" title="Expect">Section&nbsp;9.2</a>
    … …  
    904904      <div id="rfc.iref.i.1"></div>
    905905      <h3 id="rfc.section.7.1.2"><a href="#rfc.section.7.1.2">7.1.2</a>&nbsp;<a id="idempotent.methods" href="#idempotent.methods">Idempotent Methods</a></h3>
    906       <p id="rfc.section.7.1.2.p.1">Methods can also have the property of "idempotence" in that (aside from error or expiration issues) the side-effects of N
    907          &gt; 0 identical requests is the same as for a single request. The methods GET, HEAD, PUT and DELETE share this property. Also,
    908          the methods OPTIONS and TRACE <em class="bcp14">SHOULD NOT</em> have side effects, and so are inherently idempotent.
    909       </p>
    910       <p id="rfc.section.7.1.2.p.2">However, it is possible that a sequence of several requests is non-idempotent, even if all of the methods executed in that
    911          sequence are idempotent. (A sequence is idempotent if a single execution of the entire sequence always yields a result that
    912          is not changed by a reexecution of all, or part, of that sequence.) For example, a sequence is non-idempotent if its result
    913          depends on a value that is later modified in the same sequence.
    914       </p>
    915       <p id="rfc.section.7.1.2.p.3">A sequence that never has side effects is idempotent, by definition (provided that no concurrent operations are being executed
    916          on the same set of resources).
     906      <p id="rfc.section.7.1.2.p.1">Methods can also have the property of "idempotence" in that, aside from error or expiration issues, the intended effect of
     907         multiple identical requests is the same as for a single request. The methods PUT, DELETE, and all safe methods are idempotent.
     908         It is important to note that idempotence refers only to changes requested by the client: a server is free to change its state
     909         due to multiple requests for the purpose of tracking those requests, versioning of results, etc.
    917910      </p>
    918911      <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a>&nbsp;<a id="OPTIONS" href="#OPTIONS">OPTIONS</a></h2>
    … …  
    11761169      <h3 id="rfc.section.8.3.1"><a href="#rfc.section.8.3.1">8.3.1</a>&nbsp;<a id="status.300" href="#status.300">300 Multiple Choices</a></h3>
    11771170      <p id="rfc.section.8.3.1.p.1">The requested resource corresponds to any one of a set of representations, each with its own specific location, and agent-driven
    1178          negotiation information (<a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 4</a> of <a href="#Part3" id="rfc.xref.Part3.10"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) is being provided so that the user (or user agent) can select a preferred representation and redirect its request to that
     1171         negotiation information (<a href="p3-payload.html#content.negotiation" title="ERROR: Anchor 'content.negotiation' not found in p3-payload.xml.">Appendix ERROR: Anchor 'content.negotiation' not found in p3-payload.xml.</a> of <a href="#Part3" id="rfc.xref.Part3.10"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) is being provided so that the user (or user agent) can select a preferred representation and redirect its request to that
    11791172         location.
    11801173      </p>
    … …  
    15391532</pre><p id="rfc.section.9.4.p.3">An example is:</p>
    15401533      <div id="rfc.figure.u.18"></div><pre class="text">  Location: http://www.example.org/pub/WWW/People.html
    1541 </pre><div class="note">
    1542          <p> <b>Note:</b> The Content-Location header field (<a href="p3-payload.html#header.content-location" title="Content-Location">Section 5.7</a> of <a href="#Part3" id="rfc.xref.Part3.11"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) differs from Location in that the Content-Location identifies the original location of the entity enclosed in the response.
    1543             It is therefore possible for a response to contain header fields for both Location and Content-Location.
    1544          </p>
    1545       </div>
    1546       <p id="rfc.section.9.4.p.6">There are circumstances in which a fragment identifier in a Location URI would not be appropriate: </p>
     1534</pre><p id="rfc.section.9.4.p.5">There are circumstances in which a fragment identifier in a Location URI would not be appropriate: </p>
    15471535      <ul>
    15481536         <li>With a 201 Created response, because in this usage the Location header specifies the URI for the entire created resource.</li>
    15491537         <li>With 305 Use Proxy.</li>
    15501538      </ul>
     1539      <div class="note">
     1540         <p> <b>Note:</b> The Content-Location header field (<a href="p3-payload.html#header.content-location" title="ERROR: Anchor 'header.content-location' not found in p3-payload.xml.">Appendix ERROR: Anchor 'header.content-location' not found in p3-payload.xml.</a> of <a href="#Part3" id="rfc.xref.Part3.11"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) differs from Location in that the Content-Location identifies the original location of the entity enclosed in the response.
     1541            It is therefore possible for a response to contain header fields for both Location and Content-Location.
     1542         </p>
     1543      </div>
    15511544      <div id="rfc.iref.m.9"></div>
    15521545      <div id="rfc.iref.h.6"></div>
    … …  
    20802073         might be exploited. Unfortunately, this same information is often used for other valuable purposes for which HTTP currently
    20812074         has no better mechanism.
     2075      </p>
     2076      <p id="rfc.section.11.1.p.8">Some methods, like TRACE (<a href="#TRACE" id="rfc.xref.TRACE.4" title="TRACE">Section&nbsp;7.8</a>) may expose information sent in request headers in the response entity. Clients <em class="bcp14">SHOULD</em> be careful with sensitive information, like Cookies, Authorization credentials and other headers that might be used to collect
     2077         data from the Client.
    20822078      </p>
    20832079      <h2 id="rfc.section.11.2"><a href="#rfc.section.11.2">11.2</a>&nbsp;<a id="encoding.sensitive.information.in.uris" href="#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URIs</a></h2>
    … …  
    24962492      <p id="rfc.section.C.9.p.1">Closed issues: </p>
    24972493      <ul>
     2494         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/27">http://tools.ietf.org/wg/httpbis/trac/ticket/27</a>&gt;: "Idempotency"
     2495         </li>
     2496         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/33">http://tools.ietf.org/wg/httpbis/trac/ticket/33</a>&gt;: "TRACE security considerations"
     2497         </li>
    24982498         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/140">http://tools.ietf.org/wg/httpbis/trac/ticket/140</a>&gt;: "update note citing RFC 1945 and 2068"
    24992499         </li>
    … …  
    26602660                        <li class="indline1">POST&nbsp;&nbsp;<a class="iref" href="#rfc.xref.POST.1">2</a>, <a class="iref" href="#rfc.iref.m.4"><b>7.5</b></a>, <a class="iref" href="#rfc.xref.POST.2">10.1</a>, <a class="iref" href="#rfc.xref.POST.3">A.2</a></li>
    26612661                        <li class="indline1">PUT&nbsp;&nbsp;<a class="iref" href="#rfc.xref.PUT.1">2</a>, <a class="iref" href="#rfc.iref.m.5"><b>7.6</b></a>, <a class="iref" href="#rfc.xref.PUT.2">10.1</a></li>
    2662                         <li class="indline1">TRACE&nbsp;&nbsp;<a class="iref" href="#rfc.xref.TRACE.1">2</a>, <a class="iref" href="#rfc.iref.m.7"><b>7.8</b></a>, <a class="iref" href="#rfc.xref.TRACE.2">9.5</a>, <a class="iref" href="#rfc.xref.TRACE.3">10.1</a></li>
     2662                        <li class="indline1">TRACE&nbsp;&nbsp;<a class="iref" href="#rfc.xref.TRACE.1">2</a>, <a class="iref" href="#rfc.iref.m.7"><b>7.8</b></a>, <a class="iref" href="#rfc.xref.TRACE.2">9.5</a>, <a class="iref" href="#rfc.xref.TRACE.3">10.1</a>, <a class="iref" href="#rfc.xref.TRACE.4">11.1</a></li>
    26632663                        <li class="indline1">UNLINK&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.12"><b>A.1</b></a></li>
    26642664                     </ul>
    … …  
    26872687                  </li>
    26882688                  <li class="indline1"><em>Part3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.1">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.2">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.3">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.4">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.5">3</a>, <a class="iref" href="#rfc.xref.Part3.6">3</a>, <a class="iref" href="#rfc.xref.Part3.7">3</a>, <a class="iref" href="#rfc.xref.Part3.8">3</a>, <a class="iref" href="#rfc.xref.Part3.9">6</a>, <a class="iref" href="#rfc.xref.Part3.10">8.3.1</a>, <a class="iref" href="#rfc.xref.Part3.11">9.4</a>, <a class="iref" href="#Part3"><b>13.1</b></a><ul class="ind">
    2689                         <li class="indline1"><em>Section 4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.10">8.3.1</a></li>
    2690                         <li class="indline1"><em>Section 5.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.1">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.5">3</a></li>
    2691                         <li class="indline1"><em>Section 5.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.2">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.6">3</a></li>
    2692                         <li class="indline1"><em>Section 5.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.3">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.7">3</a></li>
    2693                         <li class="indline1"><em>Section 5.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.4">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.8">3</a></li>
    2694                         <li class="indline1"><em>Section 5.7</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.11">9.4</a></li>
     2689                        <li class="indline1"><em>Appendix </em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.1">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.5">3</a></li>
     2690                        <li class="indline1"><em>Appendix </em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.2">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.6">3</a></li>
     2691                        <li class="indline1"><em>Appendix </em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.3">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.7">3</a></li>
     2692                        <li class="indline1"><em>Appendix </em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.4">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.8">3</a></li>
     2693                        <li class="indline1"><em>Appendix </em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.10">8.3.1</a></li>
     2694                        <li class="indline1"><em>Appendix </em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.11">9.4</a></li>
    26952695                     </ul>
    26962696                  </li>
    … …  
    28142814            </li>
    28152815            <li class="indline0"><a id="rfc.index.T" href="#rfc.index.T"><b>T</b></a><ul class="ind">
    2816                   <li class="indline1">TRACE method&nbsp;&nbsp;<a class="iref" href="#rfc.xref.TRACE.1">2</a>, <a class="iref" href="#rfc.iref.t.1"><b>7.8</b></a>, <a class="iref" href="#rfc.xref.TRACE.2">9.5</a>, <a class="iref" href="#rfc.xref.TRACE.3">10.1</a></li>
     2816                  <li class="indline1">TRACE method&nbsp;&nbsp;<a class="iref" href="#rfc.xref.TRACE.1">2</a>, <a class="iref" href="#rfc.iref.t.1"><b>7.8</b></a>, <a class="iref" href="#rfc.xref.TRACE.2">9.5</a>, <a class="iref" href="#rfc.xref.TRACE.3">10.1</a>, <a class="iref" href="#rfc.xref.TRACE.4">11.1</a></li>
    28172817               </ul>
    28182818            </li>

  • draft-ietf-httpbis/latest/p3-payload.html

    r653 r660  
    478478         <tr>
    479479            <td class="header left"></td>
    480             <td class="header right">July 29, 2009</td>
     480            <td class="header right">July 30, 2009</td>
    481481         </tr>
    482482      </table>
    … …  
    524524      <ul class="toc">
    525525         <li class="tocline0">1.&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul class="toc">
    526                <li class="tocline1">1.1&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li>
    527                <li class="tocline1">1.2&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul class="toc">
    528                      <li class="tocline1">1.2.1&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
    529                      <li class="tocline1">1.2.2&nbsp;&nbsp;&nbsp;<a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></li>
     526               <li class="tocline1">1.1&nbsp;&nbsp;&nbsp;<a href="#terminology">Terminology</a></li>
     527               <li class="tocline1">1.2&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li>
     528               <li class="tocline1">1.3&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul class="toc">
     529                     <li class="tocline1">1.3.1&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
     530                     <li class="tocline1">1.3.2&nbsp;&nbsp;&nbsp;<a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></li>
    530531                  </ul>
    531532               </li>
    … …  
    634635         and associated requirements had become in <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
    635636      </p>
    636       <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a id="intro.requirements" href="#intro.requirements">Requirements</a></h2>
    637       <p id="rfc.section.1.1.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
     637      <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a id="terminology" href="#terminology">Terminology</a></h2>
     638      <p id="rfc.section.1.1.p.1">This specification uses a number of terms to refer to the roles played by participants in, and objects of, the HTTP communication.</p>
     639      <p id="rfc.section.1.1.p.2"> <span id="rfc.iref.c.1"></span>  <dfn>content negotiation</dfn> 
     640      </p>
     641      <dl class="empty">
     642         <dd>The mechanism for selecting the appropriate representation when servicing a request. The representation of entities in any
     643            response can be negotiated (including error responses).
     644         </dd>
     645      </dl>
     646      <p id="rfc.section.1.1.p.3"> <span id="rfc.iref.e.1"></span>  <dfn>entity</dfn> 
     647      </p>
     648      <dl class="empty">
     649         <dd>The information transferred as the payload of a request or response. An entity consists of metadata in the form of entity-header
     650            fields and content in the form of an entity-body.
     651         </dd>
     652      </dl>
     653      <p id="rfc.section.1.1.p.4"> <span id="rfc.iref.r.1"></span>  <dfn>representation</dfn> 
     654      </p>
     655      <dl class="empty">
     656         <dd>An entity included with a response that is subject to content negotiation. There may exist multiple representations associated
     657            with a particular response status.
     658         </dd>
     659      </dl>
     660      <p id="rfc.section.1.1.p.5"> <span id="rfc.iref.v.1"></span>  <dfn>variant</dfn> 
     661      </p>
     662      <dl class="empty">
     663         <dd>A resource may have one, or more than one, representation(s) associated with it at any given instant. Each of these representations
     664            is termed a `variant'. Use of the term `variant' does not necessarily imply that the resource is subject to content negotiation.
     665         </dd>
     666      </dl>
     667      <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a id="intro.requirements" href="#intro.requirements">Requirements</a></h2>
     668      <p id="rfc.section.1.2.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
    638669         in this document are to be interpreted as described in <a href="#RFC2119" id="rfc.xref.RFC2119.1"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a>.
    639670      </p>
    640       <p id="rfc.section.1.1.p.2">An implementation is not compliant if it fails to satisfy one or more of the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level requirements for the protocols it implements. An implementation that satisfies all the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level and all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "unconditionally compliant"; one that satisfies all the <em class="bcp14">MUST</em> level requirements but not all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "conditionally compliant."
    641       </p>
    642       <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a id="notation" href="#notation">Syntax Notation</a></h2>
    643       <p id="rfc.section.1.2.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> (which extends the syntax defined in <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with a list rule). <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;D</a> shows the collected ABNF, with the list rule expanded.
    644       </p>
    645       <p id="rfc.section.1.2.p.2">The following core rules are included by reference, as defined in <a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>, <a href="http://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG
     671      <p id="rfc.section.1.2.p.2">An implementation is not compliant if it fails to satisfy one or more of the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level requirements for the protocols it implements. An implementation that satisfies all the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level and all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "unconditionally compliant"; one that satisfies all the <em class="bcp14">MUST</em> level requirements but not all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "conditionally compliant."
     672      </p>
     673      <h2 id="rfc.section.1.3"><a href="#rfc.section.1.3">1.3</a>&nbsp;<a id="notation" href="#notation">Syntax Notation</a></h2>
     674      <p id="rfc.section.1.3.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> (which extends the syntax defined in <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with a list rule). <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;D</a> shows the collected ABNF, with the list rule expanded.
     675      </p>
     676      <p id="rfc.section.1.3.p.2">The following core rules are included by reference, as defined in <a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>, <a href="http://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG
    646677         (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), VCHAR (any visible USASCII character),
    647678         and WSP (whitespace).
    648679      </p>
    649       <h3 id="rfc.section.1.2.1"><a href="#rfc.section.1.2.1">1.2.1</a>&nbsp;<a id="core.rules" href="#core.rules">Core Rules</a></h3>
    650       <p id="rfc.section.1.2.1.p.1">The core rules below are 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.2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>:
     680      <h3 id="rfc.section.1.3.1"><a href="#rfc.section.1.3.1">1.3.1</a>&nbsp;<a id="core.rules" href="#core.rules">Core Rules</a></h3>
     681      <p id="rfc.section.1.3.1.p.1">The core rules below are 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.2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>:
    651682      </p>
    652683      <div id="rfc.figure.u.1"></div><pre class="inline">  <a href="#core.rules" class="smpl">quoted-string</a>  = &lt;quoted-string, defined in <a href="#Part1" id="rfc.xref.Part1.3"><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;
    653684  <a href="#core.rules" class="smpl">token</a>          = &lt;token, 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;
    654685  <a href="#core.rules" class="smpl">OWS</a>            = &lt;OWS, 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;
    655 </pre><h3 id="rfc.section.1.2.2"><a href="#rfc.section.1.2.2">1.2.2</a>&nbsp;<a id="abnf.dependencies" href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></h3>
    656       <p id="rfc.section.1.2.2.p.1">The ABNF rules below are defined in other parts:</p>
     686</pre><h3 id="rfc.section.1.3.2"><a href="#rfc.section.1.3.2">1.3.2</a>&nbsp;<a id="abnf.dependencies" href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></h3>
     687      <p id="rfc.section.1.3.2.p.1">The ABNF rules below are defined in other parts:</p>
    657688      <div id="rfc.figure.u.2"></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.6"><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.6</a>&gt;
    658689  <a href="#abnf.dependencies" class="smpl">Content-Length</a> = &lt;Content-Length, 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#header.content-length" title="Content-Length">Section 3.2</a>&gt;
    … …  
    720751         </dd>
    721752      </dl>
    722       <p id="rfc.section.2.2.p.6">compress<span id="rfc.iref.c.1"></span> 
     753      <p id="rfc.section.2.2.p.6">compress<span id="rfc.iref.c.2"></span> 
    723754      </p>
    724755      <dl class="empty">
    … …  
    869900      </p>
    870901      <p id="rfc.section.3.2.1.p.5">Note that neither the interpretation of the data type of a message nor the behaviors caused by it are defined by HTTP; this
    871          potentially includes examination of the content to override any indicated type ("sniffing")<span id="rfc.iref.c.2"></span>.
     902         potentially includes examination of the content to override any indicated type ("sniffing")<span id="rfc.iref.c.3"></span>.
    872903      </p>
    873904      <h3 id="rfc.section.3.2.2"><a href="#rfc.section.3.2.2">3.2.2</a>&nbsp;<a id="entity.length" href="#entity.length">Entity Length</a></h3>
    … …  
    11861217         </p>
    11871218      </div>
    1188       <div id="rfc.iref.c.3"></div>
     1219      <div id="rfc.iref.c.4"></div>
    11891220      <div id="rfc.iref.h.5"></div>
    11901221      <h2 id="rfc.section.5.5"><a href="#rfc.section.5.5">5.5</a>&nbsp;<a id="header.content-encoding" href="#header.content-encoding">Content-Encoding</a></h2>
    … …  
    12091240      <p id="rfc.section.5.5.p.8">If multiple encodings have been applied to an entity, the content codings <em class="bcp14">MUST</em> be listed in the order in which they were applied. Additional information about the encoding parameters <em class="bcp14">MAY</em> be provided by other entity-header fields not defined by this specification.
    12101241      </p>
    1211       <div id="rfc.iref.c.4"></div>
     1242      <div id="rfc.iref.c.5"></div>
    12121243      <div id="rfc.iref.h.6"></div>
    12131244      <h2 id="rfc.section.5.6"><a href="#rfc.section.5.6">5.6</a>&nbsp;<a id="header.content-language" href="#header.content-language">Content-Language</a></h2>
    … …  
    12351266      <p id="rfc.section.5.6.p.9">Content-Language <em class="bcp14">MAY</em> be applied to any media type -- it is not limited to textual documents.
    12361267      </p>
    1237       <div id="rfc.iref.c.5"></div>
     1268      <div id="rfc.iref.c.6"></div>
    12381269      <div id="rfc.iref.h.7"></div>
    12391270      <h2 id="rfc.section.5.7"><a href="#rfc.section.5.7">5.7</a>&nbsp;<a id="header.content-location" href="#header.content-location">Content-Location</a></h2>
    … …  
    12571288      <p id="rfc.section.5.7.p.6">If the Content-Location is a relative URI, the relative URI is interpreted relative to the request-target.</p>
    12581289      <p id="rfc.section.5.7.p.7">The meaning of the Content-Location header in requests is undefined; servers are free to ignore it in those cases.</p>
    1259       <div id="rfc.iref.c.6"></div>
     1290      <div id="rfc.iref.c.7"></div>
    12601291      <div id="rfc.iref.h.8"></div>
    12611292      <h2 id="rfc.section.5.8"><a href="#rfc.section.5.8">5.8</a>&nbsp;<a id="header.content-md5" href="#header.content-md5">Content-MD5</a></h2>
    … …  
    12951326         </p>
    12961327      </div>
    1297       <div id="rfc.iref.c.7"></div>
     1328      <div id="rfc.iref.c.8"></div>
    12981329      <div id="rfc.iref.h.9"></div>
    12991330      <h2 id="rfc.section.5.9"><a href="#rfc.section.5.9">5.9</a>&nbsp;<a id="header.content-type" href="#header.content-type">Content-Type</a></h2>
    … …  
    16811712      </p>
    16821713      <div id="rfc.iref.h.11"></div>
    1683       <div id="rfc.iref.c.8"></div>
     1714      <div id="rfc.iref.c.9"></div>
    16841715      <h2 id="rfc.section.B.1"><a href="#rfc.section.B.1">B.1</a>&nbsp;<a id="content-disposition" href="#content-disposition">Content-Disposition</a></h2>
    16851716      <p id="rfc.section.B.1.p.1">The Content-Disposition response-header field has been proposed as a means for the origin server to suggest a default filename
    … …  
    17191750      <p id="rfc.section.C.1.p.4">A content-coding of "identity" was introduced, to solve problems discovered in caching. (<a href="#content.codings" title="Content Codings">Section&nbsp;2.2</a>)
    17201751      </p>
    1721       <p id="rfc.section.C.1.p.5">The Alternates<span id="rfc.iref.a.5"></span><span id="rfc.iref.h.12"></span>, Content-Version<span id="rfc.iref.c.9"></span><span id="rfc.iref.h.13"></span>, Derived-From<span id="rfc.iref.d.2"></span><span id="rfc.iref.h.14"></span>, Link<span id="rfc.iref.l.1"></span><span id="rfc.iref.h.15"></span>, URI<span id="rfc.iref.u.1"></span><span id="rfc.iref.h.16"></span>, Public<span id="rfc.iref.p.1"></span><span id="rfc.iref.h.17"></span> and Content-Base<span id="rfc.iref.c.10"></span><span id="rfc.iref.h.18"></span> header fields were defined in previous versions of this specification, but not commonly implemented. See <a href="http://tools.ietf.org/html/rfc2068#section-19.6.2">Section 19.6.2</a> of <a href="#RFC2068" id="rfc.xref.RFC2068.5"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>.
     1752      <p id="rfc.section.C.1.p.5">The Alternates<span id="rfc.iref.a.5"></span><span id="rfc.iref.h.12"></span>, Content-Version<span id="rfc.iref.c.10"></span><span id="rfc.iref.h.13"></span>, Derived-From<span id="rfc.iref.d.2"></span><span id="rfc.iref.h.14"></span>, Link<span id="rfc.iref.l.1"></span><span id="rfc.iref.h.15"></span>, URI<span id="rfc.iref.u.1"></span><span id="rfc.iref.h.16"></span>, Public<span id="rfc.iref.p.1"></span><span id="rfc.iref.h.17"></span> and Content-Base<span id="rfc.iref.c.11"></span><span id="rfc.iref.h.18"></span> header fields were defined in previous versions of this specification, but not commonly implemented. See <a href="http://tools.ietf.org/html/rfc2068#section-19.6.2">Section 19.6.2</a> of <a href="#RFC2068" id="rfc.xref.RFC2068.5"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>.
    17221753      </p>
    17231754      <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
    … …  
    19341965      </ul>
    19351966      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
    1936       <p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.B">B</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.L">L</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.U">U</a>
     1967      <p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.B">B</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.L">L</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.U">U</a> <a href="#rfc.index.V">V</a>
    19371968      </p>
    19381969      <div class="print2col">
    … …  
    19511982            </li>
    19521983            <li class="indline0"><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul class="ind">
    1953                   <li class="indline1">compress&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.1">2.2</a></li>
    1954                   <li class="indline1">Content Type Sniffing&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.2">3.2.1</a></li>
    1955                   <li class="indline1">Content-Base header&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.10"><b>C.1</b></a></li>
    1956                   <li class="indline1">Content-Disposition header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.content-disposition.1">6.1</a>, <a class="iref" href="#rfc.xref.content-disposition.2">7.2</a>, <a class="iref" href="#rfc.iref.c.8"><b>B.1</b></a>, <a class="iref" href="#rfc.extref.c.32">B.1</a>, <a class="iref" href="#rfc.extref.c.50">D</a></li>
    1957                   <li class="indline1">Content-Encoding header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-encoding.1">2.2</a>, <a class="iref" href="#rfc.xref.header.content-encoding.2">3.1</a>, <a class="iref" href="#rfc.iref.c.3"><b>5.5</b></a>, <a class="iref" href="#rfc.xref.header.content-encoding.3">5.5</a>, <a class="iref" href="#rfc.xref.header.content-encoding.4">6.1</a></li>
    1958                   <li class="indline1">Content-Language header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-language.1">3.1</a>, <a class="iref" href="#rfc.iref.c.4"><b>5.6</b></a>, <a class="iref" href="#rfc.xref.header.content-language.2">6.1</a></li>
    1959                   <li class="indline1">Content-Location header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-location.1">3.1</a>, <a class="iref" href="#rfc.iref.c.5"><b>5.7</b></a>, <a class="iref" href="#rfc.xref.header.content-location.2">6.1</a></li>
    1960                   <li class="indline1">Content-MD5 header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-md5.1">3.1</a>, <a class="iref" href="#rfc.iref.c.6"><b>5.8</b></a>, <a class="iref" href="#rfc.xref.header.content-md5.2">6.1</a></li>
    1961                   <li class="indline1">Content-Type header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-type.1">2.3</a>, <a class="iref" href="#rfc.xref.header.content-type.2">3.1</a>, <a class="iref" href="#rfc.iref.c.7"><b>5.9</b></a>, <a class="iref" href="#rfc.xref.header.content-type.3">6.1</a></li>
    1962                   <li class="indline1">Content-Version header&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.9"><b>C.1</b></a></li>
     1984                  <li class="indline1">compress&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.2">2.2</a></li>
     1985                  <li class="indline1">content negotiation&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.1">1.1</a></li>
     1986                  <li class="indline1">Content Type Sniffing&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.3">3.2.1</a></li>
     1987                  <li class="indline1">Content-Base header&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.11"><b>C.1</b></a></li>
     1988                  <li class="indline1">Content-Disposition header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.content-disposition.1">6.1</a>, <a class="iref" href="#rfc.xref.content-disposition.2">7.2</a>, <a class="iref" href="#rfc.iref.c.9"><b>B.1</b></a>, <a class="iref" href="#rfc.extref.c.32">B.1</a>, <a class="iref" href="#rfc.extref.c.50">D</a></li>
     1989                  <li class="indline1">Content-Encoding header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-encoding.1">2.2</a>, <a class="iref" href="#rfc.xref.header.content-encoding.2">3.1</a>, <a class="iref" href="#rfc.iref.c.4"><b>5.5</b></a>, <a class="iref" href="#rfc.xref.header.content-encoding.3">5.5</a>, <a class="iref" href="#rfc.xref.header.content-encoding.4">6.1</a></li>
     1990                  <li class="indline1">Content-Language header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-language.1">3.1</a>, <a class="iref" href="#rfc.iref.c.5"><b>5.6</b></a>, <a class="iref" href="#rfc.xref.header.content-language.2">6.1</a></li>
     1991                  <li class="indline1">Content-Location header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-location.1">3.1</a>, <a class="iref" href="#rfc.iref.c.6"><b>5.7</b></a>, <a class="iref" href="#rfc.xref.header.content-location.2">6.1</a></li>
     1992                  <li class="indline1">Content-MD5 header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-md5.1">3.1</a>, <a class="iref" href="#rfc.iref.c.7"><b>5.8</b></a>, <a class="iref" href="#rfc.xref.header.content-md5.2">6.1</a></li>
     1993                  <li class="indline1">Content-Type header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-type.1">2.3</a>, <a class="iref" href="#rfc.xref.header.content-type.2">3.1</a>, <a class="iref" href="#rfc.iref.c.8"><b>5.9</b></a>, <a class="iref" href="#rfc.xref.header.content-type.3">6.1</a></li>
     1994                  <li class="indline1">Content-Version header&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.10"><b>C.1</b></a></li>
    19631995               </ul>
    19641996            </li>
    … …  
    19661998                  <li class="indline1">deflate&nbsp;&nbsp;<a class="iref" href="#rfc.iref.d.1">2.2</a></li>
    19671999                  <li class="indline1">Derived-From header&nbsp;&nbsp;<a class="iref" href="#rfc.iref.d.2"><b>C.1</b></a></li>
     2000               </ul>
     2001            </li>
     2002            <li class="indline0"><a id="rfc.index.E" href="#rfc.index.E"><b>E</b></a><ul class="ind">
     2003                  <li class="indline1">entity&nbsp;&nbsp;<a class="iref" href="#rfc.iref.e.1">1.1</a></li>
    19682004               </ul>
    19692005            </li>
    … …  
    20592095            </li>
    20602096            <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind">
    2061                   <li class="indline1"><em>Part1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.1">1.2</a>, <a class="iref" href="#rfc.xref.Part1.2">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.3">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.6">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.7">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.8">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.9">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.10">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.11">3.1</a>, <a class="iref" href="#rfc.xref.Part1.12">3.2</a>, <a class="iref" href="#rfc.xref.Part1.13">3.2.2</a>, <a class="iref" href="#rfc.xref.Part1.14">5.1</a>, <a class="iref" href="#rfc.xref.Part1.15">5.3</a>, <a class="iref" href="#Part1"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.Part1.16">A.3</a>, <a class="iref" href="#rfc.xref.Part1.17">A.6</a>, <a class="iref" href="#rfc.xref.Part1.18">C.1</a><ul class="ind">
    2062                         <li class="indline1"><em>Section 1.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.1">1.2</a></li>
    2063                         <li class="indline1"><em>Section 1.2.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.2">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.3">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.2.1</a></li>
    2064                         <li class="indline1"><em>Section 2.6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.6">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.9">1.2.2</a></li>
    2065                         <li class="indline1"><em>Section 2.7.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.8">1.2.2</a></li>
     2097                  <li class="indline1"><em>Part1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.1">1.3</a>, <a class="iref" href="#rfc.xref.Part1.2">1.3.1</a>, <a class="iref" href="#rfc.xref.Part1.3">1.3.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.3.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.3.1</a>, <a class="iref" href="#rfc.xref.Part1.6">1.3.2</a>, <a class="iref" href="#rfc.xref.Part1.7">1.3.2</a>, <a class="iref" href="#rfc.xref.Part1.8">1.3.2</a>, <a class="iref" href="#rfc.xref.Part1.9">1.3.2</a>, <a class="iref" href="#rfc.xref.Part1.10">1.3.2</a>, <a class="iref" href="#rfc.xref.Part1.11">3.1</a>, <a class="iref" href="#rfc.xref.Part1.12">3.2</a>, <a class="iref" href="#rfc.xref.Part1.13">3.2.2</a>, <a class="iref" href="#rfc.xref.Part1.14">5.1</a>, <a class="iref" href="#rfc.xref.Part1.15">5.3</a>, <a class="iref" href="#Part1"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.Part1.16">A.3</a>, <a class="iref" href="#rfc.xref.Part1.17">A.6</a>, <a class="iref" href="#rfc.xref.Part1.18">C.1</a><ul class="ind">
     2098                        <li class="indline1"><em>Section 1.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.1">1.3</a></li>
     2099                        <li class="indline1"><em>Section 1.2.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.2">1.3.1</a>, <a class="iref" href="#rfc.xref.Part1.3">1.3.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.3.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.3.1</a></li>
     2100                        <li class="indline1"><em>Section 2.6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.6">1.3.2</a>, <a class="iref" href="#rfc.xref.Part1.9">1.3.2</a></li>
     2101                        <li class="indline1"><em>Section 2.7.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.8">1.3.2</a></li>
    20662102                        <li class="indline1"><em>Section 2.7.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.12">3.2</a></li>
    20672103                        <li class="indline1"><em>Section 2.7.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.13">3.2.2</a></li>
    20682104                        <li class="indline1"><em>Section 2.10.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.16">A.3</a></li>
    2069                         <li class="indline1"><em>Section 2.10.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.10">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.14">5.1</a>, <a class="iref" href="#rfc.xref.Part1.15">5.3</a></li>
    2070                         <li class="indline1"><em>Section 3.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.7">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.11">3.1</a></li>
     2105                        <li class="indline1"><em>Section 2.10.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.10">1.3.2</a>, <a class="iref" href="#rfc.xref.Part1.14">5.1</a>, <a class="iref" href="#rfc.xref.Part1.15">5.3</a></li>
     2106                        <li class="indline1"><em>Section 3.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.7">1.3.2</a>, <a class="iref" href="#rfc.xref.Part1.11">3.1</a></li>
    20712107                        <li class="indline1"><em>Section 3.7</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.17">A.6</a></li>
    20722108                     </ul>
    … …  
    20762112                     </ul>
    20772113                  </li>
    2078                   <li class="indline1"><em>Part4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.1">1.2.2</a>, <a class="iref" href="#rfc.xref.Part4.2">3.1</a>, <a class="iref" href="#Part4"><b>9.1</b></a><ul class="ind">
    2079                         <li class="indline1"><em>Section 6.6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.1">1.2.2</a>, <a class="iref" href="#rfc.xref.Part4.2">3.1</a></li>
     2114                  <li class="indline1"><em>Part4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.1">1.3.2</a>, <a class="iref" href="#rfc.xref.Part4.2">3.1</a>, <a class="iref" href="#Part4"><b>9.1</b></a><ul class="ind">
     2115                        <li class="indline1"><em>Section 6.6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.1">1.3.2</a>, <a class="iref" href="#rfc.xref.Part4.2">3.1</a></li>
    20802116                     </ul>
    20812117                  </li>
    2082                   <li class="indline1"><em>Part5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part5.1">1.2.2</a>, <a class="iref" href="#rfc.xref.Part5.2">2.3.2</a>, <a class="iref" href="#rfc.xref.Part5.3">3.1</a>, <a class="iref" href="#Part5"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.Part5.4">C.1</a><ul class="ind">
    2083                         <li class="indline1"><em>Section 5.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part5.1">1.2.2</a>, <a class="iref" href="#rfc.xref.Part5.3">3.1</a></li>
     2118                  <li class="indline1"><em>Part5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part5.1">1.3.2</a>, <a class="iref" href="#rfc.xref.Part5.2">2.3.2</a>, <a class="iref" href="#rfc.xref.Part5.3">3.1</a>, <a class="iref" href="#Part5"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.Part5.4">C.1</a><ul class="ind">
     2119                        <li class="indline1"><em>Section 5.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part5.1">1.3.2</a>, <a class="iref" href="#rfc.xref.Part5.3">3.1</a></li>
    20842120                        <li class="indline1"><em>Appendix A</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part5.2">2.3.2</a></li>
    20852121                     </ul>
    20862122                  </li>
    2087                   <li class="indline1"><em>Part6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.1">1.2.2</a>, <a class="iref" href="#rfc.xref.Part6.2">3.1</a>, <a class="iref" href="#rfc.xref.Part6.3">4.1</a>, <a class="iref" href="#rfc.xref.Part6.4">5.7</a>, <a class="iref" href="#Part6"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.Part6.5">C.1</a><ul class="ind">
     2123                  <li class="indline1"><em>Part6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.1">1.3.2</a>, <a class="iref" href="#rfc.xref.Part6.2">3.1</a>, <a class="iref" href="#rfc.xref.Part6.3">4.1</a>, <a class="iref" href="#rfc.xref.Part6.4">5.7</a>, <a class="iref" href="#Part6"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.Part6.5">C.1</a><ul class="ind">
    20882124                        <li class="indline1"><em>Section 2.6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.4">5.7</a></li>
    2089                         <li class="indline1"><em>Section 3.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.1">1.2.2</a>, <a class="iref" href="#rfc.xref.Part6.2">3.1</a></li>
     2125                        <li class="indline1"><em>Section 3.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.1">1.3.2</a>, <a class="iref" href="#rfc.xref.Part6.2">3.1</a></li>
    20902126                        <li class="indline1"><em>Section 3.5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.3">4.1</a></li>
    20912127                     </ul>
    … …  
    20952131            </li>
    20962132            <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind">
     2133                  <li class="indline1">representation&nbsp;&nbsp;<a class="iref" href="#rfc.iref.r.1">1.1</a></li>
    20972134                  <li class="indline1"><em>RFC1864</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1864.1">5.8</a>, <a class="iref" href="#rfc.xref.RFC1864.2">5.8</a>, <a class="iref" href="#RFC1864"><b>9.1</b></a></li>
    20982135                  <li class="indline1"><em>RFC1945</em>&nbsp;&nbsp;<a class="iref" href="#RFC1945"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC1945.1">B</a></li>
    … …  
    21152152                  </li>
    21162153                  <li class="indline1"><em>RFC2076</em>&nbsp;&nbsp;<a class="iref" href="#RFC2076"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2076.1">B</a></li>
    2117                   <li class="indline1"><em>RFC2119</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>9.1</b></a></li>
     2154                  <li class="indline1"><em>RFC2119</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2119.1">1.2</a>, <a class="iref" href="#RFC2119"><b>9.1</b></a></li>
    21182155                  <li class="indline1"><em>RFC2183</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2183.1">7.2</a>, <a class="iref" href="#rfc.xref.RFC2183.2">7.2</a>, <a class="iref" href="#RFC2183"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2183.3">B.1</a><ul class="ind">
    21192156                        <li class="indline1"><em>Section 5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2183.2">7.2</a></li>
    … …  
    21362173                     </ul>
    21372174                  </li>
    2138                   <li class="indline1"><em>RFC5234</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5234.1">1.2</a>, <a class="iref" href="#rfc.xref.RFC5234.2">1.2</a>, <a class="iref" href="#RFC5234"><b>9.1</b></a><ul class="ind">
    2139                         <li class="indline1"><em>Appendix B.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5234.2">1.2</a></li>
     2175                  <li class="indline1"><em>RFC5234</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5234.1">1.3</a>, <a class="iref" href="#rfc.xref.RFC5234.2">1.3</a>, <a class="iref" href="#RFC5234"><b>9.1</b></a><ul class="ind">
     2176                        <li class="indline1"><em>Appendix B.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5234.2">1.3</a></li>
    21402177                     </ul>
    21412178                  </li>
    … …  
    21472184               </ul>
    21482185            </li>
     2186            <li class="indline0"><a id="rfc.index.V" href="#rfc.index.V"><b>V</b></a><ul class="ind">
     2187                  <li class="indline1">variant&nbsp;&nbsp;<a class="iref" href="#rfc.iref.v.1">1.1</a></li>
     2188               </ul>
     2189            </li>
    21492190         </ul>
    21502191      </div>

  • draft-ietf-httpbis/latest/p3-payload.xml

    r653 r660  
    236236   requirements had become in <xref target="RFC2616"/>.
    237237</t>
     238
     239<section title="Terminology" anchor="terminology">
     240<t>
     241   This specification uses a number of terms to refer to the roles
     242   played by participants in, and objects of, the HTTP communication.
     243</t>
     244<t>
     245  <iref item="content negotiation"/>
     246  <x:dfn>content negotiation</x:dfn>
     247  <list>
     248    <t>
     249      The mechanism for selecting the appropriate representation when
     250      servicing a request. The representation of entities in any response
     251      can be negotiated (including error responses).
     252    </t>
     253  </list>
     254</t>
     255<t>
     256  <iref item="entity"/>
     257  <x:dfn>entity</x:dfn>
     258  <list>
     259    <t>
     260      The information transferred as the payload of a request or
     261      response. An entity consists of metadata in the form of
     262      entity-header fields and content in the form of an entity-body.
     263    </t>
     264  </list>
     265</t>
     266<t>
     267  <iref item="representation"/>
     268  <x:dfn>representation</x:dfn>
     269  <list>
     270    <t>
     271      An entity included with a response that is subject to content
     272      negotiation. There may exist multiple
     273      representations associated with a particular response status.
     274    </t>
     275  </list>
     276</t>
     277<t>
     278  <iref item="variant"/>
     279  <x:dfn>variant</x:dfn>
     280  <list>
     281    <t>
     282      A resource may have one, or more than one, representation(s)
     283      associated with it at any given instant. Each of these
     284      representations is termed a `variant'.  Use of the term `variant'
     285      does not necessarily imply that the resource is subject to content
     286      negotiation.
     287    </t>
     288  </list>
     289</t>
     290</section>
    238291
    239292<section title="Requirements" anchor="intro.requirements">

  • draft-ietf-httpbis/latest/p4-conditional.html

    r653 r660  
    467467         <tr>
    468468            <td class="header left"></td>
    469             <td class="header right">July 29, 2009</td>
     469            <td class="header right">July 30, 2009</td>
    470470         </tr>
    471471      </table>
    … …  
    877877         then the server <em class="bcp14">MAY</em> perform the requested method as if the If-Match header field did not exist.
    878878      </p>
    879       <p id="rfc.section.6.2.p.4">A server <em class="bcp14">MUST</em> use the strong comparison function (see <a href="#weak.and.strong.validators" title="Weak and Strong Validators">Section&nbsp;4</a>) to compare the entity tags in If-Match.
    880       </p>
    881       <p id="rfc.section.6.2.p.5">If none of the entity tags match, or if "*" is given and no current entity exists, the server <em class="bcp14">MUST NOT</em> perform the requested method, and <em class="bcp14">MUST</em> return a 412 (Precondition Failed) response. This behavior is most useful when the client wants to prevent an updating method,
     879      <p id="rfc.section.6.2.p.4">If none of the entity tags match, or if "*" is given and no current entity exists, the server <em class="bcp14">MUST NOT</em> perform the requested method, and <em class="bcp14">MUST</em> return a 412 (Precondition Failed) response. This behavior is most useful when the client wants to prevent an updating method,
    882880         such as PUT, from modifying a resource that has changed since the client last retrieved it.
    883881      </p>
    884       <p id="rfc.section.6.2.p.6">If the request would, without the If-Match header field, result in anything other than a 2xx or 412 status, then the If-Match
     882      <p id="rfc.section.6.2.p.5">If the request would, without the If-Match header field, result in anything other than a 2xx or 412 status, then the If-Match
    885883         header <em class="bcp14">MUST</em> be ignored.
    886884      </p>
    887       <p id="rfc.section.6.2.p.7">The meaning of "If-Match: *" is that the method <em class="bcp14">SHOULD</em> be performed if the representation selected by the origin server (or by a cache, possibly using the Vary mechanism, see <a href="p6-cache.html#header.vary" title="Vary">Section 3.5</a> of <a href="#Part6" id="rfc.xref.Part6.2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) exists, and <em class="bcp14">MUST NOT</em> be performed if the representation does not exist.
    888       </p>
    889       <p id="rfc.section.6.2.p.8">A request intended to update a resource (e.g., a PUT) <em class="bcp14">MAY</em> include an If-Match header field to signal that the request method <em class="bcp14">MUST NOT</em> be applied if the entity corresponding to the If-Match value (a single entity tag) is no longer a representation of that resource.
     885      <p id="rfc.section.6.2.p.6">The meaning of "If-Match: *" is that the method <em class="bcp14">SHOULD</em> be performed if the representation selected by the origin server (or by a cache, possibly using the Vary mechanism, see <a href="p6-cache.html#header.vary" title="Vary">Section 3.5</a> of <a href="#Part6" id="rfc.xref.Part6.2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) exists, and <em class="bcp14">MUST NOT</em> be performed if the representation does not exist.
     886      </p>
     887      <p id="rfc.section.6.2.p.7">A request intended to update a resource (e.g., a PUT) <em class="bcp14">MAY</em> include an If-Match header field to signal that the request method <em class="bcp14">MUST NOT</em> be applied if the entity corresponding to the If-Match value (a single entity tag) is no longer a representation of that resource.
    890888         This allows the user to indicate that they do not wish the request to be successful if the resource has been changed without
    891889         their knowledge. Examples:
    … …  
    894892  If-Match: "xyzzy", "r2d2xxxx", "c3piozzzz"
    895893  If-Match: *
    896 </pre><p id="rfc.section.6.2.p.10">The result of a request having both an If-Match header field and either an If-None-Match or an If-Modified-Since header fields
     894</pre><p id="rfc.section.6.2.p.9">The result of a request having both an If-Match header field and either an If-None-Match or an If-Modified-Since header fields
    897895         is undefined by this specification.
    898896      </p>
    … …  
    962960         that matched. For all other request methods, the server <em class="bcp14">MUST</em> respond with a status of 412 (Precondition Failed).
    963961      </p>
    964       <p id="rfc.section.6.4.p.5">See <a href="#weak.and.strong.validators" title="Weak and Strong Validators">Section&nbsp;4</a> for rules on how to determine if two entity tags match.
    965       </p>
    966       <p id="rfc.section.6.4.p.6">If none of the entity tags match, then the server <em class="bcp14">MAY</em> perform the requested method as if the If-None-Match header field did not exist, but <em class="bcp14">MUST</em> also ignore any If-Modified-Since header field(s) in the request. That is, if no entity tags match, then the server <em class="bcp14">MUST NOT</em> return a 304 (Not Modified) response.
    967       </p>
    968       <p id="rfc.section.6.4.p.7">If the request would, without the If-None-Match header field, result in anything other than a 2xx or 304 status, then the
     962      <p id="rfc.section.6.4.p.5">If none of the entity tags match, then the server <em class="bcp14">MAY</em> perform the requested method as if the If-None-Match header field did not exist, but <em class="bcp14">MUST</em> also ignore any If-Modified-Since header field(s) in the request. That is, if no entity tags match, then the server <em class="bcp14">MUST NOT</em> return a 304 (Not Modified) response.
     963      </p>
     964      <p id="rfc.section.6.4.p.6">If the request would, without the If-None-Match header field, result in anything other than a 2xx or 304 status, then the
    969965         If-None-Match header <em class="bcp14">MUST</em> be ignored. (See <a href="#rules.for.when.to.use.entity.tags.and.last-modified.dates" title="Rules for When to Use Entity Tags and Last-Modified Dates">Section&nbsp;5</a> for a discussion of server behavior when both If-Modified-Since and If-None-Match appear in the same request.)
    970966      </p>
    971       <p id="rfc.section.6.4.p.8">The meaning of "If-None-Match: *" is that the method <em class="bcp14">MUST NOT</em> be performed if the representation selected by the origin server (or by a cache, possibly using the Vary mechanism, see <a href="p6-cache.html#header.vary" title="Vary">Section 3.5</a> of <a href="#Part6" id="rfc.xref.Part6.3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) exists, and <em class="bcp14">SHOULD</em> be performed if the representation does not exist. This feature is intended to be useful in preventing races between PUT operations.
    972       </p>
    973       <p id="rfc.section.6.4.p.9">Examples:</p>
     967      <p id="rfc.section.6.4.p.7">The meaning of "If-None-Match: *" is that the method <em class="bcp14">MUST NOT</em> be performed if the representation selected by the origin server (or by a cache, possibly using the Vary mechanism, see <a href="p6-cache.html#header.vary" title="Vary">Section 3.5</a> of <a href="#Part6" id="rfc.xref.Part6.3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) exists, and <em class="bcp14">SHOULD</em> be performed if the representation does not exist. This feature is intended to be useful in preventing races between PUT operations.
     968      </p>
     969      <p id="rfc.section.6.4.p.8">Examples:</p>
    974970      <div id="rfc.figure.u.11"></div><pre class="text">  If-None-Match: "xyzzy"
    975971  If-None-Match: W/"xyzzy"
    … …  
    977973  If-None-Match: W/"xyzzy", W/"r2d2xxxx", W/"c3piozzzz"
    978974  If-None-Match: *
    979 </pre><p id="rfc.section.6.4.p.11">The result of a request having both an If-None-Match header field and either an If-Match or an If-Unmodified-Since header
     975</pre><p id="rfc.section.6.4.p.10">The result of a request having both an If-None-Match header field and either an If-Match or an If-Unmodified-Since header
    980976         fields is undefined by this specification.
    981977      </p>
    … …  
    12601256      </ul>
    12611257      <h2 id="rfc.section.C.9"><a href="#rfc.section.C.9">C.9</a>&nbsp;<a id="changes.since.07" href="#changes.since.07">Since draft-ietf-httpbis-p4-conditional-07</a></h2>
    1262       <p id="rfc.section.C.9.p.1">None.</p>
     1258      <p id="rfc.section.C.9.p.1">Closed issues: </p>
     1259      <ul>
     1260         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/116">http://tools.ietf.org/wg/httpbis/trac/ticket/116</a>&gt;: "Weak ETags on non-GET requests" (If-Match still was defined to require strong matching)
     1261         </li>
     1262      </ul>
    12631263      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
    12641264      <p class="noprint"><a href="#rfc.index.3">3</a> <a href="#rfc.index.4">4</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.L">L</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a>
Note: See TracChangeset for help on using the changeset viewer.