Changeset 1798


Ignore:
Timestamp:
Jul 15, 2012, 11:01:00 PM (7 years ago)
Author:
julian.reschke@…
Message:

Move ABNF extension (list production) to appendix.

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

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p0-introduction.html

    r1776 r1798  
    393393  }
    394394  @bottom-center {
    395        content: "Expires January 15, 2013";
     395       content: "Expires January 17, 2013";
    396396  }
    397397  @bottom-right {
     
    426426      <meta name="dct.creator" content="Reschke, J. F.">
    427427      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p0-introduction-latest">
    428       <meta name="dct.issued" scheme="ISO8601" content="2012-07-14">
     428      <meta name="dct.issued" scheme="ISO8601" content="2012-07-16">
    429429      <meta name="dct.abstract" content="This document is the first in a series that, collectively, define the HyperText Transfer Protocol, version 1.1; otherwise known as HTTP/1.1.">
    430430      <meta name="description" content="This document is the first in a series that, collectively, define the HyperText Transfer Protocol, version 1.1; otherwise known as HTTP/1.1.">
     
    446446            </tr>
    447447            <tr>
    448                <td class="left">Expires: January 15, 2013</td>
     448               <td class="left">Expires: January 17, 2013</td>
    449449               <td class="right">W3C</td>
    450450            </tr>
     
    467467            <tr>
    468468               <td class="left"></td>
    469                <td class="right">July 14, 2012</td>
     469               <td class="right">July 16, 2012</td>
    470470            </tr>
    471471         </tbody>
     
    490490         in progress”.
    491491      </p>
    492       <p>This Internet-Draft will expire on January 15, 2013.</p>
     492      <p>This Internet-Draft will expire on January 17, 2013.</p>
    493493      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    494494      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
  • draft-ietf-httpbis/latest/p1-messaging.html

    r1796 r1798  
    482482      <link rel="Chapter" href="#rfc.section.10" title="10 References">
    483483      <link rel="Appendix" title="A HTTP Version History" href="#rfc.section.A">
    484       <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B">
    485       <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C">
     484      <link rel="Appendix" title="B ABNF list extension: #rule" href="#rfc.section.B">
     485      <link rel="Appendix" title="C Collected ABNF" href="#rfc.section.C">
     486      <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D">
    486487      <link href="p2-semantics.html" rel="next">
    487488      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.584, 2012-06-24 15:59:38, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     
    544545      <p>The current issues list is at &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/report/3">http://tools.ietf.org/wg/httpbis/trac/report/3</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;.
    545546      </p> 
    546       <p>The changes in this draft are summarized in <a href="#changes.since.19" title="Since draft-ietf-httpbis-p1-messaging-19">Appendix&nbsp;C.21</a>.
     547      <p>The changes in this draft are summarized in <a href="#changes.since.19" title="Since draft-ietf-httpbis-p1-messaging-19">Appendix&nbsp;D.21</a>.
    547548      </p>
    548549      <h1><a id="rfc.status" href="#rfc.status">Status of This Memo</a></h1>
     
    605606                     <li>3.2.3&nbsp;&nbsp;&nbsp;<a href="#field.length">Field Length</a></li>
    606607                     <li>3.2.4&nbsp;&nbsp;&nbsp;<a href="#field.components">Field value components</a></li>
    607                      <li>3.2.5&nbsp;&nbsp;&nbsp;<a href="#abnf.extension">ABNF list extension: #rule</a></li>
    608608                  </ul>
    609609               </li>
     
    711711            </ul>
    712712         </li>
    713          <li>B.&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
    714          <li>C.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
    715                <li>C.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.1">Since RFC 2616</a></li>
    716                <li>C.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.2">Since draft-ietf-httpbis-p1-messaging-00</a></li>
    717                <li>C.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.3">Since draft-ietf-httpbis-p1-messaging-01</a></li>
    718                <li>C.4&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p1-messaging-02</a></li>
    719                <li>C.5&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p1-messaging-03</a></li>
    720                <li>C.6&nbsp;&nbsp;&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p1-messaging-04</a></li>
    721                <li>C.7&nbsp;&nbsp;&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-p1-messaging-05</a></li>
    722                <li>C.8&nbsp;&nbsp;&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-p1-messaging-06</a></li>
    723                <li>C.9&nbsp;&nbsp;&nbsp;<a href="#changes.since.07">Since draft-ietf-httpbis-p1-messaging-07</a></li>
    724                <li>C.10&nbsp;&nbsp;&nbsp;<a href="#changes.since.08">Since draft-ietf-httpbis-p1-messaging-08</a></li>
    725                <li>C.11&nbsp;&nbsp;&nbsp;<a href="#changes.since.09">Since draft-ietf-httpbis-p1-messaging-09</a></li>
    726                <li>C.12&nbsp;&nbsp;&nbsp;<a href="#changes.since.10">Since draft-ietf-httpbis-p1-messaging-10</a></li>
    727                <li>C.13&nbsp;&nbsp;&nbsp;<a href="#changes.since.11">Since draft-ietf-httpbis-p1-messaging-11</a></li>
    728                <li>C.14&nbsp;&nbsp;&nbsp;<a href="#changes.since.12">Since draft-ietf-httpbis-p1-messaging-12</a></li>
    729                <li>C.15&nbsp;&nbsp;&nbsp;<a href="#changes.since.13">Since draft-ietf-httpbis-p1-messaging-13</a></li>
    730                <li>C.16&nbsp;&nbsp;&nbsp;<a href="#changes.since.14">Since draft-ietf-httpbis-p1-messaging-14</a></li>
    731                <li>C.17&nbsp;&nbsp;&nbsp;<a href="#changes.since.15">Since draft-ietf-httpbis-p1-messaging-15</a></li>
    732                <li>C.18&nbsp;&nbsp;&nbsp;<a href="#changes.since.16">Since draft-ietf-httpbis-p1-messaging-16</a></li>
    733                <li>C.19&nbsp;&nbsp;&nbsp;<a href="#changes.since.17">Since draft-ietf-httpbis-p1-messaging-17</a></li>
    734                <li>C.20&nbsp;&nbsp;&nbsp;<a href="#changes.since.18">Since draft-ietf-httpbis-p1-messaging-18</a></li>
    735                <li>C.21&nbsp;&nbsp;&nbsp;<a href="#changes.since.19">Since draft-ietf-httpbis-p1-messaging-19</a></li>
     713         <li>B.&nbsp;&nbsp;&nbsp;<a href="#abnf.extension">ABNF list extension: #rule</a></li>
     714         <li>C.&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
     715         <li>D.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
     716               <li>D.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.1">Since RFC 2616</a></li>
     717               <li>D.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.2">Since draft-ietf-httpbis-p1-messaging-00</a></li>
     718               <li>D.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.3">Since draft-ietf-httpbis-p1-messaging-01</a></li>
     719               <li>D.4&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p1-messaging-02</a></li>
     720               <li>D.5&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p1-messaging-03</a></li>
     721               <li>D.6&nbsp;&nbsp;&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p1-messaging-04</a></li>
     722               <li>D.7&nbsp;&nbsp;&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-p1-messaging-05</a></li>
     723               <li>D.8&nbsp;&nbsp;&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-p1-messaging-06</a></li>
     724               <li>D.9&nbsp;&nbsp;&nbsp;<a href="#changes.since.07">Since draft-ietf-httpbis-p1-messaging-07</a></li>
     725               <li>D.10&nbsp;&nbsp;&nbsp;<a href="#changes.since.08">Since draft-ietf-httpbis-p1-messaging-08</a></li>
     726               <li>D.11&nbsp;&nbsp;&nbsp;<a href="#changes.since.09">Since draft-ietf-httpbis-p1-messaging-09</a></li>
     727               <li>D.12&nbsp;&nbsp;&nbsp;<a href="#changes.since.10">Since draft-ietf-httpbis-p1-messaging-10</a></li>
     728               <li>D.13&nbsp;&nbsp;&nbsp;<a href="#changes.since.11">Since draft-ietf-httpbis-p1-messaging-11</a></li>
     729               <li>D.14&nbsp;&nbsp;&nbsp;<a href="#changes.since.12">Since draft-ietf-httpbis-p1-messaging-12</a></li>
     730               <li>D.15&nbsp;&nbsp;&nbsp;<a href="#changes.since.13">Since draft-ietf-httpbis-p1-messaging-13</a></li>
     731               <li>D.16&nbsp;&nbsp;&nbsp;<a href="#changes.since.14">Since draft-ietf-httpbis-p1-messaging-14</a></li>
     732               <li>D.17&nbsp;&nbsp;&nbsp;<a href="#changes.since.15">Since draft-ietf-httpbis-p1-messaging-15</a></li>
     733               <li>D.18&nbsp;&nbsp;&nbsp;<a href="#changes.since.16">Since draft-ietf-httpbis-p1-messaging-16</a></li>
     734               <li>D.19&nbsp;&nbsp;&nbsp;<a href="#changes.since.17">Since draft-ietf-httpbis-p1-messaging-17</a></li>
     735               <li>D.20&nbsp;&nbsp;&nbsp;<a href="#changes.since.18">Since draft-ietf-httpbis-p1-messaging-18</a></li>
     736               <li>D.21&nbsp;&nbsp;&nbsp;<a href="#changes.since.19">Since draft-ietf-httpbis-p1-messaging-19</a></li>
    736737            </ul>
    737738         </li>
     
    796797      <div id="rfc.iref.g.12"></div>
    797798      <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>
    798       <p id="rfc.section.1.2.p.1">This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with the list rule extension defined in <a href="#abnf.extension" title="ABNF list extension: #rule">Section&nbsp;3.2.5</a>. <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;B</a> shows the collected ABNF with the list rule expanded.
     799      <p id="rfc.section.1.2.p.1">This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with the list rule extension defined in <a href="#abnf.extension" title="ABNF list extension: #rule">Appendix&nbsp;B</a>. <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;C</a> shows the collected ABNF with the list rule expanded.
    799800      </p>
    800801      <div id="core.rules">
     
    13611362         ")").
    13621363      </p>
    1363       <h3 id="rfc.section.3.2.5"><a href="#rfc.section.3.2.5">3.2.5</a>&nbsp;<a id="abnf.extension" href="#abnf.extension">ABNF list extension: #rule</a></h3>
    1364       <p id="rfc.section.3.2.5.p.1">A #rule extension to the ABNF rules of <a href="#RFC5234" id="rfc.xref.RFC5234.3"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> is used to improve readability in the definitions of some header field values.
    1365       </p>
    1366       <p id="rfc.section.3.2.5.p.2">A construct "#" is defined, similar to "*", for defining comma-delimited lists of elements. The full form is "&lt;n&gt;#&lt;m&gt;element"
    1367          indicating at least &lt;n&gt; and at most &lt;m&gt; elements, each separated by a single comma (",") and optional whitespace (OWS).
    1368       </p>
    1369       <div id="rfc.figure.u.25"></div>
    1370       <p>Thus,</p><pre class="text">  1#element =&gt; element *( OWS "," OWS element )
    1371 </pre><div id="rfc.figure.u.26"></div>
    1372       <p>and:</p><pre class="text">  #element =&gt; [ 1#element ]
    1373 </pre><div id="rfc.figure.u.27"></div>
    1374       <p>and for n &gt;= 1 and m &gt; 1:</p><pre class="text">  &lt;n&gt;#&lt;m&gt;element =&gt; element &lt;n-1&gt;*&lt;m-1&gt;( OWS "," OWS element )
    1375 </pre><p id="rfc.section.3.2.5.p.6">For compatibility with legacy list rules, recipients <em class="bcp14">SHOULD</em> accept empty list elements. In other words, consumers would follow the list productions:
    1376       </p>
    1377       <div id="rfc.figure.u.28"></div><pre class="text">  #element =&gt; [ ( "," / element ) *( OWS "," [ OWS element ] ) ]
    1378  
    1379   1#element =&gt; *( "," OWS ) element *( OWS "," [ OWS element ] )
    1380 </pre><p id="rfc.section.3.2.5.p.8">Note that empty elements do not contribute to the count of elements present, though.</p>
    1381       <p id="rfc.section.3.2.5.p.9">For example, given these ABNF productions:</p>
    1382       <div id="rfc.figure.u.29"></div><pre class="text">  example-list      = 1#example-list-elmt
    1383   example-list-elmt = token ; see <a href="#field.components" title="Field value components">Section&nbsp;3.2.4</a>
    1384 </pre><p id="rfc.section.3.2.5.p.11">Then these are valid values for example-list (not including the double quotes, which are present for delimitation only):</p>
    1385       <div id="rfc.figure.u.30"></div><pre class="text">  "foo,bar"
    1386   "foo ,bar,"
    1387   "foo , ,bar,charlie   "
    1388 </pre><p id="rfc.section.3.2.5.p.13">But these values would be invalid, as at least one non-empty element is required:</p>
    1389       <div id="rfc.figure.u.31"></div><pre class="text">  ""
    1390   ","
    1391   ",   ,"
    1392 </pre><p id="rfc.section.3.2.5.p.15"> <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;B</a> shows the collected ABNF, with the list rules expanded as explained above.
    1393       </p>
    13941364      <h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;<a id="message.body" href="#message.body">Message Body</a></h2>
    13951365      <p id="rfc.section.3.3.p.1">The message body (if any) of an HTTP message is used to carry the payload body of that request or response. The message body
    13961366         is identical to the payload body unless a transfer coding has been applied, as described in <a href="#header.transfer-encoding" id="rfc.xref.header.transfer-encoding.1" title="Transfer-Encoding">Section&nbsp;3.3.1</a>.
    13971367      </p>
    1398       <div id="rfc.figure.u.32"></div><pre class="inline"><span id="rfc.iref.g.52"></span>  <a href="#message.body" class="smpl">message-body</a> = *OCTET
     1368      <div id="rfc.figure.u.25"></div><pre class="inline"><span id="rfc.iref.g.52"></span>  <a href="#message.body" class="smpl">message-body</a> = *OCTET
    13991369</pre><p id="rfc.section.3.3.p.3">The rules for when a message body is allowed in a message differ for requests and responses.</p>
    14001370      <p id="rfc.section.3.3.p.4">The presence of a message body in a request is signaled by a a <a href="#header.content-length" class="smpl">Content-Length</a> or <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding</a> header field. Request message framing is independent of method semantics, even if the method does not define any use for a
     
    14111381         in <a href="#transfer.codings" title="Transfer Codings">Section&nbsp;4</a>.
    14121382      </p>
    1413       <div id="rfc.figure.u.33"></div><pre class="inline"><span id="rfc.iref.g.53"></span>  <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding</a> = 1#<a href="#transfer.codings" class="smpl">transfer-coding</a>
     1383      <div id="rfc.figure.u.26"></div><pre class="inline"><span id="rfc.iref.g.53"></span>  <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding</a> = 1#<a href="#transfer.codings" class="smpl">transfer-coding</a>
    14141384</pre><p id="rfc.section.3.3.1.p.3">Transfer-Encoding is analogous to the Content-Transfer-Encoding field of MIME, which was designed to enable safe transport
    14151385         of binary data over a 7-bit transport service (<a href="#RFC2045" id="rfc.xref.RFC2045.2"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a>, <a href="http://tools.ietf.org/html/rfc2045#section-6">Section 6</a>). However, safe transport has a different focus for an 8bit-clean transfer protocol. In HTTP's case, Transfer-Encoding is
     
    14211391         applied <em class="bcp14">MUST</em> be "chunked". If any transfer-coding is applied to a response payload body, then either the final transfer-coding applied <em class="bcp14">MUST</em> be "chunked" or the message <em class="bcp14">MUST</em> be terminated by closing the connection.
    14221392      </p>
    1423       <div id="rfc.figure.u.34"></div>
     1393      <div id="rfc.figure.u.27"></div>
    14241394      <p>For example,</p><pre class="text">  Transfer-Encoding: gzip, chunked
    14251395</pre><p>indicates that the payload body has been compressed using the gzip coding and then chunked using the chunked coding while
     
    14461416         other than <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a>, or would have been present had the request been an unconditional GET. The length is expressed as a decimal number of octets.
    14471417      </p>
    1448       <div id="rfc.figure.u.35"></div><pre class="inline"><span id="rfc.iref.g.54"></span>  <a href="#header.content-length" class="smpl">Content-Length</a> = 1*<a href="#core.rules" class="smpl">DIGIT</a>
     1418      <div id="rfc.figure.u.28"></div><pre class="inline"><span id="rfc.iref.g.54"></span>  <a href="#header.content-length" class="smpl">Content-Length</a> = 1*<a href="#core.rules" class="smpl">DIGIT</a>
    14491419</pre><p id="rfc.section.3.3.2.p.3">An example is</p>
    1450       <div id="rfc.figure.u.36"></div><pre class="text">  Content-Length: 3495
     1420      <div id="rfc.figure.u.29"></div><pre class="text">  Content-Length: 3495
    14511421</pre><p id="rfc.section.3.3.2.p.5">In the case of a response to a HEAD request, Content-Length indicates the size of the payload body (without any potential
    14521422         transfer-coding) that would have been sent had the request been a GET. In the case of a <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> response (<a href="p4-conditional.html#status.304" title="304 Not Modified">Section 4.1</a> of <a href="#Part4" id="rfc.xref.Part4.3"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>) to a GET request, Content-Length indicates the size of the payload body (without any potential transfer-coding) that would
     
    15691539         transfer-coding is a property of the message rather than a property of the representation that is being transferred.
    15701540      </p>
    1571       <div id="rfc.figure.u.37"></div><pre class="inline"><span id="rfc.iref.g.55"></span><span id="rfc.iref.g.56"></span>  <a href="#transfer.codings" class="smpl">transfer-coding</a>    = "chunked" ; <a href="#chunked.encoding" title="Chunked Transfer Coding">Section&nbsp;4.1</a>
     1541      <div id="rfc.figure.u.30"></div><pre class="inline"><span id="rfc.iref.g.55"></span><span id="rfc.iref.g.56"></span>  <a href="#transfer.codings" class="smpl">transfer-coding</a>    = "chunked" ; <a href="#chunked.encoding" title="Chunked Transfer Coding">Section&nbsp;4.1</a>
    15721542                     / "compress" ; <a href="#compress.coding" title="Compress Coding">Section&nbsp;4.2.1</a>
    15731543                     / "deflate" ; <a href="#deflate.coding" title="Deflate Coding">Section&nbsp;4.2.2</a>
     
    15781548         <p id="rfc.section.4.p.3">      Parameters are in the form of attribute/value pairs.</p>
    15791549      </div>
    1580       <div id="rfc.figure.u.38"></div><pre class="inline"><span id="rfc.iref.g.57"></span><span id="rfc.iref.g.58"></span><span id="rfc.iref.g.59"></span><span id="rfc.iref.g.60"></span><span id="rfc.iref.g.61"></span>  <a href="#rule.parameter" class="smpl">transfer-parameter</a> = <a href="#rule.parameter" class="smpl">attribute</a> <a href="#rule.whitespace" class="smpl">BWS</a> "=" <a href="#rule.whitespace" class="smpl">BWS</a> <a href="#rule.parameter" class="smpl">value</a>
     1550      <div id="rfc.figure.u.31"></div><pre class="inline"><span id="rfc.iref.g.57"></span><span id="rfc.iref.g.58"></span><span id="rfc.iref.g.59"></span><span id="rfc.iref.g.60"></span><span id="rfc.iref.g.61"></span>  <a href="#rule.parameter" class="smpl">transfer-parameter</a> = <a href="#rule.parameter" class="smpl">attribute</a> <a href="#rule.whitespace" class="smpl">BWS</a> "=" <a href="#rule.whitespace" class="smpl">BWS</a> <a href="#rule.parameter" class="smpl">value</a>
    15811551  <a href="#rule.parameter" class="smpl">attribute</a>          = <a href="#rule.token.separators" class="smpl">token</a>
    15821552  <a href="#rule.parameter" class="smpl">value</a>              = <a href="#rule.token.separators" class="smpl">word</a>
     
    15901560         for the recipient to verify that it has received the full message.
    15911561      </p>
    1592       <div id="rfc.figure.u.39"></div><pre class="inline"><span id="rfc.iref.g.62"></span><span id="rfc.iref.g.63"></span><span id="rfc.iref.g.64"></span><span id="rfc.iref.g.65"></span><span id="rfc.iref.g.66"></span><span id="rfc.iref.g.67"></span><span id="rfc.iref.g.68"></span><span id="rfc.iref.g.69"></span><span id="rfc.iref.g.70"></span><span id="rfc.iref.g.71"></span><span id="rfc.iref.g.72"></span>  <a href="#chunked.encoding" class="smpl">chunked-body</a>   = *<a href="#chunked.encoding" class="smpl">chunk</a>
     1562      <div id="rfc.figure.u.32"></div><pre class="inline"><span id="rfc.iref.g.62"></span><span id="rfc.iref.g.63"></span><span id="rfc.iref.g.64"></span><span id="rfc.iref.g.65"></span><span id="rfc.iref.g.66"></span><span id="rfc.iref.g.67"></span><span id="rfc.iref.g.68"></span><span id="rfc.iref.g.69"></span><span id="rfc.iref.g.70"></span><span id="rfc.iref.g.71"></span><span id="rfc.iref.g.72"></span>  <a href="#chunked.encoding" class="smpl">chunked-body</a>   = *<a href="#chunked.encoding" class="smpl">chunk</a>
    15931563                   <a href="#chunked.encoding" class="smpl">last-chunk</a>
    15941564                   <a href="#chunked.encoding" class="smpl">trailer-part</a>
     
    16301600      </p>
    16311601      <p id="rfc.section.4.1.p.7">A process for decoding the "chunked" transfer-coding can be represented in pseudo-code as:</p>
    1632       <div id="rfc.figure.u.40"></div><pre class="text">  length := 0
     1602      <div id="rfc.figure.u.33"></div><pre class="text">  length := 0
    16331603  read chunk-size, chunk-ext (if any) and CRLF
    16341604  while (chunk-size &gt; 0) {
     
    16891659         accept parameters (as described in <a href="#transfer.codings" title="Transfer Codings">Section&nbsp;4</a>).
    16901660      </p>
    1691       <div id="rfc.figure.u.41"></div><pre class="inline"><span id="rfc.iref.g.74"></span><span id="rfc.iref.g.75"></span><span id="rfc.iref.g.76"></span><span id="rfc.iref.g.77"></span>  <a href="#header.te" class="smpl">TE</a>        = #<a href="#header.te" class="smpl">t-codings</a>
     1661      <div id="rfc.figure.u.34"></div><pre class="inline"><span id="rfc.iref.g.74"></span><span id="rfc.iref.g.75"></span><span id="rfc.iref.g.76"></span><span id="rfc.iref.g.77"></span>  <a href="#header.te" class="smpl">TE</a>        = #<a href="#header.te" class="smpl">t-codings</a>
    16921662  <a href="#header.te" class="smpl">t-codings</a> = "trailers" / ( <a href="#transfer.codings" class="smpl">transfer-extension</a> [ <a href="#header.te" class="smpl">te-params</a> ] )
    16931663  <a href="#header.te" class="smpl">te-params</a> = <a href="#rule.whitespace" class="smpl">OWS</a> ";" <a href="#rule.whitespace" class="smpl">OWS</a> "q=" <a href="#quality.values" class="smpl">qvalue</a> *( <a href="#header.te" class="smpl">te-ext</a> )
     
    16971667      </p>
    16981668      <p id="rfc.section.4.3.p.5">Examples of its use are:</p>
    1699       <div id="rfc.figure.u.42"></div><pre class="text">  TE: deflate
     1669      <div id="rfc.figure.u.35"></div><pre class="text">  TE: deflate
    17001670  TE:
    17011671  TE: trailers, deflate;q=0.5
     
    17331703         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.
    17341704      </p>
    1735       <div id="rfc.figure.u.43"></div><pre class="inline"><span id="rfc.iref.g.78"></span>  <a href="#quality.values" class="smpl">qvalue</a>         = ( "0" [ "." 0*3<a href="#core.rules" class="smpl">DIGIT</a> ] )
     1705      <div id="rfc.figure.u.36"></div><pre class="inline"><span id="rfc.iref.g.78"></span>  <a href="#quality.values" class="smpl">qvalue</a>         = ( "0" [ "." 0*3<a href="#core.rules" class="smpl">DIGIT</a> ] )
    17361706                 / ( "1" [ "." 0*3("0") ] )
    17371707</pre><div class="note" id="rfc.section.4.3.1.p.3">
     
    17451715         chunked transfer-coding.
    17461716      </p>
    1747       <div id="rfc.figure.u.44"></div><pre class="inline"><span id="rfc.iref.g.79"></span>  <a href="#header.trailer" class="smpl">Trailer</a> = 1#<a href="#header.fields" class="smpl">field-name</a>
     1717      <div id="rfc.figure.u.37"></div><pre class="inline"><span id="rfc.iref.g.79"></span>  <a href="#header.trailer" class="smpl">Trailer</a> = 1#<a href="#header.fields" class="smpl">field-name</a>
    17481718</pre><p id="rfc.section.4.4.p.3">An HTTP/1.1 message <em class="bcp14">SHOULD</em> include a Trailer header field in a message using chunked transfer-coding with a non-empty trailer. Doing so allows the recipient
    17491719         to know which header fields to expect in the trailer.
     
    17961766         both the method being requested and whether the request is to a proxy.
    17971767      </p>
    1798       <div id="rfc.figure.u.45"></div><pre class="inline"><span id="rfc.iref.g.80"></span><span id="rfc.iref.g.81"></span><span id="rfc.iref.g.82"></span><span id="rfc.iref.g.83"></span><span id="rfc.iref.g.84"></span>  <a href="#request-target" class="smpl">request-target</a> = <a href="#origin-form" class="smpl">origin-form</a>
     1768      <div id="rfc.figure.u.38"></div><pre class="inline"><span id="rfc.iref.g.80"></span><span id="rfc.iref.g.81"></span><span id="rfc.iref.g.82"></span><span id="rfc.iref.g.83"></span><span id="rfc.iref.g.84"></span>  <a href="#request-target" class="smpl">request-target</a> = <a href="#origin-form" class="smpl">origin-form</a>
    17991769                 / <a href="#absolute-form" class="smpl">absolute-form</a>
    18001770                 / <a href="#authority-form" class="smpl">authority-form</a>
     
    18121782      </div>
    18131783      <p id="rfc.section.5.3.p.4">For example, a client wishing to retrieve a representation of the resource identified as</p>
    1814       <div id="rfc.figure.u.46"></div><pre class="text">http://www.example.org/where?q=now
     1784      <div id="rfc.figure.u.39"></div><pre class="text">http://www.example.org/where?q=now
    18151785</pre><p id="rfc.section.5.3.p.6">directly from the origin server would open (or reuse) a TCP connection to port 80 of the host "www.example.org" and send the
    18161786         lines:
    18171787      </p>
    1818       <div id="rfc.figure.u.47"></div><pre class="text2">GET /where?q=now HTTP/1.1
     1788      <div id="rfc.figure.u.40"></div><pre class="text2">GET /where?q=now HTTP/1.1
    18191789Host: www.example.org
    18201790</pre><p id="rfc.section.5.3.p.8">followed by the remainder of the request message.</p>
     
    18261796      </div>
    18271797      <p id="rfc.section.5.3.p.10">An example absolute-form of request-line would be:</p>
    1828       <div id="rfc.figure.u.48"></div><pre class="text2">GET http://www.example.org/pub/WWW/TheProject.html HTTP/1.1
     1798      <div id="rfc.figure.u.41"></div><pre class="text2">GET http://www.example.org/pub/WWW/TheProject.html HTTP/1.1
    18291799</pre><p id="rfc.section.5.3.p.12">To allow for transition to the absolute-form for all requests in some future version of HTTP, HTTP/1.1 servers <em class="bcp14">MUST</em> accept the absolute-form in requests, even though HTTP/1.1 clients will only send them in requests to proxies.
    18301800      </p>
     
    18331803         </p>
    18341804      </div>
    1835       <div id="rfc.figure.u.49"></div><pre class="text2">CONNECT www.example.com:80 HTTP/1.1
     1805      <div id="rfc.figure.u.42"></div><pre class="text2">CONNECT www.example.com:80 HTTP/1.1
    18361806</pre><div id="asterisk-form">
    18371807         <p id="rfc.section.5.3.p.15"><span id="rfc.iref.a.4"></span> The asterisk-form of request-target is only used for a server-wide OPTIONS request (<a href="p2-semantics.html#OPTIONS" title="OPTIONS">Section 2.3.1</a> of <a href="#Part2" id="rfc.xref.Part2.14"><cite title="HTTP/1.1, part 2: Message Semantics, Payload and Content Negotiation">[Part2]</cite></a>). When a client wishes to request OPTIONS for the server as a whole, as opposed to a specific named resource of that server,
     
    18391809         </p>
    18401810      </div>
    1841       <div id="rfc.figure.u.50"></div><pre class="text2">OPTIONS * HTTP/1.1
     1811      <div id="rfc.figure.u.43"></div><pre class="text2">OPTIONS * HTTP/1.1
    18421812</pre><p id="rfc.section.5.3.p.17">If a proxy receives an OPTIONS request with an absolute-form of request-target in which the URI has an empty path and no query
    18431813         component, then the last proxy on the request chain <em class="bcp14">MUST</em> send a request-target of "*" when it forwards the request to the indicated origin server.
    18441814      </p>
    1845       <div id="rfc.figure.u.51"></div>
     1815      <div id="rfc.figure.u.44"></div>
    18461816      <p>For example, the request</p><pre class="text2">OPTIONS http://www.example.org:8001 HTTP/1.1
    1847 </pre><div id="rfc.figure.u.52"></div>
     1817</pre><div id="rfc.figure.u.45"></div>
    18481818      <p>would be forwarded by the final proxy as</p><pre class="text2">OPTIONS * HTTP/1.1
    18491819Host: www.example.org:8001
     
    18561826         is critical information for handling a request, it <em class="bcp14">SHOULD</em> be sent as the first header field following the request-line.
    18571827      </p>
    1858       <div id="rfc.figure.u.53"></div><pre class="inline"><span id="rfc.iref.g.85"></span>  <a href="#header.host" class="smpl">Host</a> = <a href="#uri" class="smpl">uri-host</a> [ ":" <a href="#uri" class="smpl">port</a> ] ; <a href="#http.uri" title="http URI scheme">Section&nbsp;2.8.1</a>
     1828      <div id="rfc.figure.u.46"></div><pre class="inline"><span id="rfc.iref.g.85"></span>  <a href="#header.host" class="smpl">Host</a> = <a href="#uri" class="smpl">uri-host</a> [ ":" <a href="#uri" class="smpl">port</a> ] ; <a href="#http.uri" title="http URI scheme">Section&nbsp;2.8.1</a>
    18591829</pre><p id="rfc.section.5.4.p.3">A client <em class="bcp14">MUST</em> send a Host header field in all HTTP/1.1 request messages. If the target URI includes an authority component, then the Host
    18601830         field-value <em class="bcp14">MUST</em> be identical to that authority component after excluding any userinfo (<a href="#http.uri" title="http URI scheme">Section&nbsp;2.8.1</a>). If the authority component is missing or undefined for the target URI, then the Host header field <em class="bcp14">MUST</em> be sent with an empty field-value.
    18611831      </p>
    18621832      <p id="rfc.section.5.4.p.4">For example, a GET request to the origin server for &lt;http://www.example.org/pub/WWW/&gt; would begin with:</p>
    1863       <div id="rfc.figure.u.54"></div><pre class="text2">GET /pub/WWW/ HTTP/1.1
     1833      <div id="rfc.figure.u.47"></div><pre class="text2">GET /pub/WWW/ HTTP/1.1
    18641834Host: www.example.org
    18651835</pre><p id="rfc.section.5.4.p.6">The Host header field <em class="bcp14">MUST</em> be sent in an HTTP/1.1 request even if the request-target is in the absolute-form, since this allows the Host information
     
    19001870         the scheme, "://", authority, and combined path and query component.
    19011871      </p>
    1902       <div id="rfc.figure.u.55"></div>
     1872      <div id="rfc.figure.u.48"></div>
    19031873      <p>Example 1: the following message received over an insecure TCP connection</p>  <pre class="text">GET /pub/WWW/TheProject.html HTTP/1.1
    19041874Host: www.example.org:8080
    1905 </pre> <div id="rfc.figure.u.56"></div>
     1875</pre> <div id="rfc.figure.u.49"></div>
    19061876      <p>has an effective request URI of</p>  <pre class="text">http://www.example.org:8080/pub/WWW/TheProject.html
    1907 </pre> <div id="rfc.figure.u.57"></div>
     1877</pre> <div id="rfc.figure.u.50"></div>
    19081878      <p>Example 2: the following message received over an SSL/TLS-secured TCP connection</p>  <pre class="text">OPTIONS * HTTP/1.1
    19091879Host: www.example.org
    1910 </pre> <div id="rfc.figure.u.58"></div>
     1880</pre> <div id="rfc.figure.u.51"></div>
    19111881      <p>has an effective request URI of</p>  <pre class="text">https://www.example.org
    19121882</pre> <p id="rfc.section.5.5.p.12">An origin server that does not allow resources to differ by requested host <em class="bcp14">MAY</em> ignore the <a href="#header.host" class="smpl">Host</a> field-value and instead replace it with a configured server name when constructing the effective request URI.
     
    20231993      </p>
    20241994      <p id="rfc.section.6.1.p.2">The Connection header field's value has the following grammar:</p>
    2025       <div id="rfc.figure.u.59"></div><pre class="inline"><span id="rfc.iref.g.86"></span><span id="rfc.iref.g.87"></span>  <a href="#header.connection" class="smpl">Connection</a>        = 1#<a href="#header.connection" class="smpl">connection-option</a>
     1995      <div id="rfc.figure.u.52"></div><pre class="inline"><span id="rfc.iref.g.86"></span><span id="rfc.iref.g.87"></span>  <a href="#header.connection" class="smpl">Connection</a>        = 1#<a href="#header.connection" class="smpl">connection-option</a>
    20261996  <a href="#header.connection" class="smpl">connection-option</a> = <a href="#rule.token.separators" class="smpl">token</a>
    20271997</pre><p id="rfc.section.6.1.p.4">Connection options are compared case-insensitively.</p>
     
    20482018         of the response. For example,
    20492019      </p>
    2050       <div id="rfc.figure.u.60"></div><pre class="text">  Connection: close
     2020      <div id="rfc.figure.u.53"></div><pre class="text">  Connection: close
    20512021</pre><p id="rfc.section.6.1.p.11">in either the request or the response header fields indicates that the connection <em class="bcp14">SHOULD NOT</em> be considered "persistent" (<a href="#persistent.connections" title="Persistent Connections">Section&nbsp;6.3</a>) after the current request/response is complete.
    20522022      </p>
     
    20632033         of all senders along the request/response chain.
    20642034      </p>
    2065       <div id="rfc.figure.u.61"></div><pre class="inline"><span id="rfc.iref.g.88"></span><span id="rfc.iref.g.89"></span><span id="rfc.iref.g.90"></span><span id="rfc.iref.g.91"></span><span id="rfc.iref.g.92"></span><span id="rfc.iref.g.93"></span>  <a href="#header.via" class="smpl">Via</a>               = 1#( <a href="#header.via" class="smpl">received-protocol</a> <a href="#rule.whitespace" class="smpl">RWS</a> <a href="#header.via" class="smpl">received-by</a>
     2035      <div id="rfc.figure.u.54"></div><pre class="inline"><span id="rfc.iref.g.88"></span><span id="rfc.iref.g.89"></span><span id="rfc.iref.g.90"></span><span id="rfc.iref.g.91"></span><span id="rfc.iref.g.92"></span><span id="rfc.iref.g.93"></span>  <a href="#header.via" class="smpl">Via</a>               = 1#( <a href="#header.via" class="smpl">received-protocol</a> <a href="#rule.whitespace" class="smpl">RWS</a> <a href="#header.via" class="smpl">received-by</a>
    20662036                          [ <a href="#rule.whitespace" class="smpl">RWS</a> <a href="#rule.comment" class="smpl">comment</a> ] )
    20672037  <a href="#header.via" class="smpl">received-protocol</a> = [ <a href="#header.upgrade" class="smpl">protocol-name</a> "/" ] <a href="#header.upgrade" class="smpl">protocol-version</a>
     
    20842054         server at www.example.com. The request received by www.example.com would then have the following Via header field:
    20852055      </p>
    2086       <div id="rfc.figure.u.62"></div><pre class="text">  Via: 1.0 fred, 1.1 p.example.net (Apache/1.1)
     2056      <div id="rfc.figure.u.55"></div><pre class="text">  Via: 1.0 fred, 1.1 p.example.net (Apache/1.1)
    20872057</pre><p id="rfc.section.6.2.p.9">A proxy or gateway used as a portal through a network firewall <em class="bcp14">SHOULD NOT</em> forward the names and ports of hosts within the firewall region unless it is explicitly enabled to do so. If not enabled,
    20882058         the received-by host of any host behind the firewall <em class="bcp14">SHOULD</em> be replaced by an appropriate pseudonym for that host.
     
    20912061         For example,
    20922062      </p>
    2093       <div id="rfc.figure.u.63"></div><pre class="text">  Via: 1.0 ricky, 1.1 ethel, 1.1 fred, 1.0 lucy
     2063      <div id="rfc.figure.u.56"></div><pre class="text">  Via: 1.0 ricky, 1.1 ethel, 1.1 fred, 1.0 lucy
    20942064</pre><p id="rfc.section.6.2.p.12">could be collapsed to</p>
    2095       <div id="rfc.figure.u.64"></div><pre class="text">  Via: 1.0 ricky, 1.1 mertz, 1.0 lucy
     2065      <div id="rfc.figure.u.57"></div><pre class="text">  Via: 1.0 ricky, 1.1 mertz, 1.0 lucy
    20962066</pre><p id="rfc.section.6.2.p.14">Senders <em class="bcp14">SHOULD NOT</em> combine multiple entries unless they are all under the same organizational control and the hosts have already been replaced
    20972067         by pseudonyms. Senders <em class="bcp14">MUST NOT</em> combine entries which have different received-protocol values.
     
    22552225         server chooses to switch protocols. Servers can use it to indicate what protocols they are willing to switch to.
    22562226      </p>
    2257       <div id="rfc.figure.u.65"></div><pre class="inline"><span id="rfc.iref.g.94"></span>  <a href="#header.upgrade" class="smpl">Upgrade</a>          = 1#<a href="#header.upgrade" class="smpl">protocol</a>
     2227      <div id="rfc.figure.u.58"></div><pre class="inline"><span id="rfc.iref.g.94"></span>  <a href="#header.upgrade" class="smpl">Upgrade</a>          = 1#<a href="#header.upgrade" class="smpl">protocol</a>
    22582228
    22592229  <a href="#header.upgrade" class="smpl">protocol</a>         = <a href="#header.upgrade" class="smpl">protocol-name</a> ["/" <a href="#header.upgrade" class="smpl">protocol-version</a>]
     
    22612231  <a href="#header.upgrade" class="smpl">protocol-version</a> = <a href="#rule.token.separators" class="smpl">token</a>
    22622232</pre><p id="rfc.section.6.5.p.3">For example,</p>
    2263       <div id="rfc.figure.u.66"></div><pre class="text">  Upgrade: HTTP/2.0, SHTTP/1.3, IRC/6.9, RTA/x11
     2233      <div id="rfc.figure.u.59"></div><pre class="text">  Upgrade: HTTP/2.0, SHTTP/1.3, IRC/6.9, RTA/x11
    22642234</pre><p id="rfc.section.6.5.p.5">The Upgrade header field is intended to provide a simple mechanism for transitioning from HTTP/1.1 to some other, incompatible
    22652235         protocol. It does so by allowing the client to advertise its desire to use another protocol, such as a later version of HTTP
     
    30182988         rule was removed). (<a href="#field.components" title="Field value components">Section&nbsp;3.2.4</a>)
    30192989      </p>
    3020       <p id="rfc.section.A.2.p.6">Empty list elements in list productions have been deprecated. (<a href="#abnf.extension" title="ABNF list extension: #rule">Section&nbsp;3.2.5</a>)
     2990      <p id="rfc.section.A.2.p.6">Empty list elements in list productions have been deprecated. (<a href="#abnf.extension" title="ABNF list extension: #rule">Appendix&nbsp;B</a>)
    30212991      </p>
    30222992      <p id="rfc.section.A.2.p.7">Require recipients to handle bogus <a href="#header.content-length" class="smpl">Content-Length</a> header fields as errors. (<a href="#message.body" title="Message Body">Section&nbsp;3.3</a>)
     
    30413011      <p id="rfc.section.A.2.p.16">Take over the Upgrade Token Registry, previously defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.2">Section 7.2</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.4"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#upgrade.token.registry" title="Upgrade Token Registry">Section&nbsp;7.6</a>)
    30423012      </p>
    3043       <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
     3013      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="abnf.extension" href="#abnf.extension">ABNF list extension: #rule</a></h1>
     3014      <p id="rfc.section.B.p.1">A #rule extension to the ABNF rules of <a href="#RFC5234" id="rfc.xref.RFC5234.3"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> is used to improve readability in the definitions of some header field values.
     3015      </p>
     3016      <p id="rfc.section.B.p.2">A construct "#" is defined, similar to "*", for defining comma-delimited lists of elements. The full form is "&lt;n&gt;#&lt;m&gt;element"
     3017         indicating at least &lt;n&gt; and at most &lt;m&gt; elements, each separated by a single comma (",") and optional whitespace (OWS).
     3018      </p>
     3019      <div id="rfc.figure.u.60"></div>
     3020      <p>Thus,</p><pre class="text">  1#element =&gt; element *( OWS "," OWS element )
     3021</pre><div id="rfc.figure.u.61"></div>
     3022      <p>and:</p><pre class="text">  #element =&gt; [ 1#element ]
     3023</pre><div id="rfc.figure.u.62"></div>
     3024      <p>and for n &gt;= 1 and m &gt; 1:</p><pre class="text">  &lt;n&gt;#&lt;m&gt;element =&gt; element &lt;n-1&gt;*&lt;m-1&gt;( OWS "," OWS element )
     3025</pre><p id="rfc.section.B.p.6">For compatibility with legacy list rules, recipients <em class="bcp14">SHOULD</em> accept empty list elements. In other words, consumers would follow the list productions:
     3026      </p>
     3027      <div id="rfc.figure.u.63"></div><pre class="text">  #element =&gt; [ ( "," / element ) *( OWS "," [ OWS element ] ) ]
     3028 
     3029  1#element =&gt; *( "," OWS ) element *( OWS "," [ OWS element ] )
     3030</pre><p id="rfc.section.B.p.8">Note that empty elements do not contribute to the count of elements present, though.</p>
     3031      <p id="rfc.section.B.p.9">For example, given these ABNF productions:</p>
     3032      <div id="rfc.figure.u.64"></div><pre class="text">  example-list      = 1#example-list-elmt
     3033  example-list-elmt = token ; see <a href="#field.components" title="Field value components">Section&nbsp;3.2.4</a>
     3034</pre><p id="rfc.section.B.p.11">Then these are valid values for example-list (not including the double quotes, which are present for delimitation only):</p>
     3035      <div id="rfc.figure.u.65"></div><pre class="text">  "foo,bar"
     3036  "foo ,bar,"
     3037  "foo , ,bar,charlie   "
     3038</pre><p id="rfc.section.B.p.13">But these values would be invalid, as at least one non-empty element is required:</p>
     3039      <div id="rfc.figure.u.66"></div><pre class="text">  ""
     3040  ","
     3041  ",   ,"
     3042</pre><p id="rfc.section.B.p.15"> <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;C</a> shows the collected ABNF, with the list rules expanded as explained above.
     3043      </p>
     3044      <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
    30443045      <div id="rfc.figure.u.67"></div> <pre class="inline"><a href="#rule.whitespace" class="smpl">BWS</a> = OWS
    30453046
     
    31613162
    31623163<a href="#rule.token.separators" class="smpl">word</a> = token / quoted-string
    3163 </pre> <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
    3164       <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a>&nbsp;Since RFC 2616
     3164</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>
     3165      <h2 id="rfc.section.D.1"><a href="#rfc.section.D.1">D.1</a>&nbsp;Since RFC 2616
    31653166      </h2>
    3166       <p id="rfc.section.C.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.6"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
    3167       </p>
    3168       <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a>&nbsp;Since draft-ietf-httpbis-p1-messaging-00
     3167      <p id="rfc.section.D.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.6"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
     3168      </p>
     3169      <h2 id="rfc.section.D.2"><a href="#rfc.section.D.2">D.2</a>&nbsp;Since draft-ietf-httpbis-p1-messaging-00
    31693170      </h2>
    3170       <p id="rfc.section.C.2.p.1">Closed issues: </p>
     3171      <p id="rfc.section.D.2.p.1">Closed issues: </p>
    31713172      <ul>
    31723173         <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;)
     
    32093210         </li>
    32103211      </ul>
    3211       <p id="rfc.section.C.2.p.2">Other changes: </p>
     3212      <p id="rfc.section.D.2.p.2">Other changes: </p>
    32123213      <ul>
    32133214         <li>Update media type registrations to use RFC4288 template.</li>
     
    32153216         </li>
    32163217      </ul>
    3217       <h2 id="rfc.section.C.3"><a href="#rfc.section.C.3">C.3</a>&nbsp;Since draft-ietf-httpbis-p1-messaging-01
     3218      <h2 id="rfc.section.D.3"><a href="#rfc.section.D.3">D.3</a>&nbsp;Since draft-ietf-httpbis-p1-messaging-01
    32183219      </h2>
    3219       <p id="rfc.section.C.3.p.1">Closed issues: </p>
     3220      <p id="rfc.section.D.3.p.1">Closed issues: </p>
    32203221      <ul>
    32213222         <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"
     
    32283229         </li>
    32293230      </ul>
    3230       <p id="rfc.section.C.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;):
     3231      <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;):
    32313232      </p>
    32323233      <ul>
     
    32433244         <li>Rewrite prose rule "token" in terms of "tchar", rewrite prose rule "TEXT".</li>
    32443245      </ul>
    3245       <h2 id="rfc.section.C.4"><a href="#rfc.section.C.4">C.4</a>&nbsp;<a id="changes.since.02" href="#changes.since.02">Since draft-ietf-httpbis-p1-messaging-02</a></h2>
    3246       <p id="rfc.section.C.4.p.1">Closed issues: </p>
     3246      <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>
     3247      <p id="rfc.section.D.4.p.1">Closed issues: </p>
    32473248      <ul>
    32483249         <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"
     
    32513252         </li>
    32523253      </ul>
    3253       <p id="rfc.section.C.4.p.2">Ongoing work on IANA Message Header Field Registration (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>&gt;):
     3254      <p id="rfc.section.D.4.p.2">Ongoing work on IANA Message Header Field Registration (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>&gt;):
    32543255      </p>
    32553256      <ul>
    32563257         <li>Reference RFC 3984, and update header field registrations for header fields defined in this document.</li>
    32573258      </ul>
    3258       <p id="rfc.section.C.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;):
     3259      <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;):
    32593260      </p>
    32603261      <ul>
    32613262         <li>Replace string literals when the string really is case-sensitive (HTTP-version).</li>
    32623263      </ul>
    3263       <h2 id="rfc.section.C.5"><a href="#rfc.section.C.5">C.5</a>&nbsp;<a id="changes.since.03" href="#changes.since.03">Since draft-ietf-httpbis-p1-messaging-03</a></h2>
    3264       <p id="rfc.section.C.5.p.1">Closed issues: </p>
     3264      <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>
     3265      <p id="rfc.section.D.5.p.1">Closed issues: </p>
    32653266      <ul>
    32663267         <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"
     
    32773278         </li>
    32783279      </ul>
    3279       <p id="rfc.section.C.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;):
     3280      <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;):
    32803281      </p>
    32813282      <ul>
     
    32833284         <li>Replace HEX by HEXDIG for future consistence with RFC 5234's core rules.</li>
    32843285      </ul>
    3285       <h2 id="rfc.section.C.6"><a href="#rfc.section.C.6">C.6</a>&nbsp;<a id="changes.since.04" href="#changes.since.04">Since draft-ietf-httpbis-p1-messaging-04</a></h2>
    3286       <p id="rfc.section.C.6.p.1">Closed issues: </p>
     3286      <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>
     3287      <p id="rfc.section.D.6.p.1">Closed issues: </p>
    32873288      <ul>
    32883289         <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"
     
    32913292         </li>
    32923293      </ul>
    3293       <p id="rfc.section.C.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;):
     3294      <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;):
    32943295      </p>
    32953296      <ul>
     
    33003301         <li>Rewrite ABNFs to spell out whitespace rules, factor out header field value format definitions.</li>
    33013302      </ul>
    3302       <h2 id="rfc.section.C.7"><a href="#rfc.section.C.7">C.7</a>&nbsp;<a id="changes.since.05" href="#changes.since.05">Since draft-ietf-httpbis-p1-messaging-05</a></h2>
    3303       <p id="rfc.section.C.7.p.1">Closed issues: </p>
     3303      <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>
     3304      <p id="rfc.section.D.7.p.1">Closed issues: </p>
    33043305      <ul>
    33053306         <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"
     
    33243325         </li>
    33253326      </ul>
    3326       <p id="rfc.section.C.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;):
     3327      <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;):
    33273328      </p>
    33283329      <ul>
     
    33303331         <li>Add appendix containing collected and expanded ABNF.</li>
    33313332      </ul>
    3332       <p id="rfc.section.C.7.p.3">Other changes: </p>
     3333      <p id="rfc.section.D.7.p.3">Other changes: </p>
    33333334      <ul>
    33343335         <li>Rewrite introduction; add mostly new Architecture Section.</li>
     
    33373338         </li>
    33383339      </ul>
    3339       <h2 id="rfc.section.C.8"><a href="#rfc.section.C.8">C.8</a>&nbsp;<a id="changes.since.06" href="#changes.since.06">Since draft-ietf-httpbis-p1-messaging-06</a></h2>
    3340       <p id="rfc.section.C.8.p.1">Closed issues: </p>
     3340      <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>
     3341      <p id="rfc.section.D.8.p.1">Closed issues: </p>
    33413342      <ul>
    33423343         <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"
     
    33453346         </li>
    33463347      </ul>
    3347       <p id="rfc.section.C.8.p.2">Partly resolved issues: </p>
     3348      <p id="rfc.section.D.8.p.2">Partly resolved issues: </p>
    33483349      <ul>
    33493350         <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 might be methods for which a request body MUST NOT be included)
     
    33523353         </li>
    33533354      </ul>
    3354       <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-p1-messaging-07</a></h2>
    3355       <p id="rfc.section.C.9.p.1">Closed issues: </p>
     3355      <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>
     3356      <p id="rfc.section.D.9.p.1">Closed issues: </p>
    33563357      <ul>
    33573358         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/93">http://tools.ietf.org/wg/httpbis/trac/ticket/93</a>&gt;: "Repeating single-value header fields"
     
    33743375         </li>
    33753376      </ul>
    3376       <p id="rfc.section.C.9.p.2">Partly resolved issues: </p>
     3377      <p id="rfc.section.D.9.p.2">Partly resolved issues: </p>
    33773378      <ul>
    33783379         <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)
    33793380         </li>
    33803381      </ul>
    3381       <h2 id="rfc.section.C.10"><a href="#rfc.section.C.10">C.10</a>&nbsp;<a id="changes.since.08" href="#changes.since.08">Since draft-ietf-httpbis-p1-messaging-08</a></h2>
    3382       <p id="rfc.section.C.10.p.1">Closed issues: </p>
     3382      <h2 id="rfc.section.D.10"><a href="#rfc.section.D.10">D.10</a>&nbsp;<a id="changes.since.08" href="#changes.since.08">Since draft-ietf-httpbis-p1-messaging-08</a></h2>
     3383      <p id="rfc.section.D.10.p.1">Closed issues: </p>
    33833384      <ul>
    33843385         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/201">http://tools.ietf.org/wg/httpbis/trac/ticket/201</a>&gt;: "header parsing, treatment of leading and trailing OWS"
    33853386         </li>
    33863387      </ul>
    3387       <p id="rfc.section.C.10.p.2">Partly resolved issues: </p>
     3388      <p id="rfc.section.D.10.p.2">Partly resolved issues: </p>
    33883389      <ul>
    33893390         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/60">http://tools.ietf.org/wg/httpbis/trac/ticket/60</a>&gt;: "Placement of 13.5.1 and 13.5.2"
     
    33923393         </li>
    33933394      </ul>
    3394       <h2 id="rfc.section.C.11"><a href="#rfc.section.C.11">C.11</a>&nbsp;<a id="changes.since.09" href="#changes.since.09">Since draft-ietf-httpbis-p1-messaging-09</a></h2>
    3395       <p id="rfc.section.C.11.p.1">Closed issues: </p>
     3395      <h2 id="rfc.section.D.11"><a href="#rfc.section.D.11">D.11</a>&nbsp;<a id="changes.since.09" href="#changes.since.09">Since draft-ietf-httpbis-p1-messaging-09</a></h2>
     3396      <p id="rfc.section.D.11.p.1">Closed issues: </p>
    33963397      <ul>
    33973398         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/73">http://tools.ietf.org/wg/httpbis/trac/ticket/73</a>&gt;: "Clarification of the term 'deflate'"
     
    34083409         </li>
    34093410      </ul>
    3410       <p id="rfc.section.C.11.p.2">Partly resolved issues: </p>
     3411      <p id="rfc.section.D.11.p.2">Partly resolved issues: </p>
    34113412      <ul>
    34123413         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/196">http://tools.ietf.org/wg/httpbis/trac/ticket/196</a>&gt;: "Term for the requested resource's URI"
    34133414         </li>
    34143415      </ul>
    3415       <h2 id="rfc.section.C.12"><a href="#rfc.section.C.12">C.12</a>&nbsp;<a id="changes.since.10" href="#changes.since.10">Since draft-ietf-httpbis-p1-messaging-10</a></h2>
    3416       <p id="rfc.section.C.12.p.1">Closed issues: </p>
     3416      <h2 id="rfc.section.D.12"><a href="#rfc.section.D.12">D.12</a>&nbsp;<a id="changes.since.10" href="#changes.since.10">Since draft-ietf-httpbis-p1-messaging-10</a></h2>
     3417      <p id="rfc.section.D.12.p.1">Closed issues: </p>
    34173418      <ul>
    34183419         <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"
     
    34273428         </li>
    34283429      </ul>
    3429       <p id="rfc.section.C.12.p.2">Partly resolved issues: </p>
     3430      <p id="rfc.section.D.12.p.2">Partly resolved issues: </p>
    34303431      <ul>
    34313432         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/159">http://tools.ietf.org/wg/httpbis/trac/ticket/159</a>&gt;: "HTTP(s) URI scheme definitions"
    34323433         </li>
    34333434      </ul>
    3434       <h2 id="rfc.section.C.13"><a href="#rfc.section.C.13">C.13</a>&nbsp;<a id="changes.since.11" href="#changes.since.11">Since draft-ietf-httpbis-p1-messaging-11</a></h2>
    3435       <p id="rfc.section.C.13.p.1">Closed issues: </p>
     3435      <h2 id="rfc.section.D.13"><a href="#rfc.section.D.13">D.13</a>&nbsp;<a id="changes.since.11" href="#changes.since.11">Since draft-ietf-httpbis-p1-messaging-11</a></h2>
     3436      <p id="rfc.section.D.13.p.1">Closed issues: </p>
    34363437      <ul>
    34373438         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/193">http://tools.ietf.org/wg/httpbis/trac/ticket/193</a>&gt;: "Trailer requirements"
     
    34443445         </li>
    34453446      </ul>
    3446       <p id="rfc.section.C.13.p.2">Partly resolved issues: </p>
     3447      <p id="rfc.section.D.13.p.2">Partly resolved issues: </p>
    34473448      <ul>
    34483449         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/95">http://tools.ietf.org/wg/httpbis/trac/ticket/95</a>&gt;: "Handling multiple Content-Length header fields"
    34493450         </li>
    34503451      </ul>
    3451       <h2 id="rfc.section.C.14"><a href="#rfc.section.C.14">C.14</a>&nbsp;<a id="changes.since.12" href="#changes.since.12">Since draft-ietf-httpbis-p1-messaging-12</a></h2>
    3452       <p id="rfc.section.C.14.p.1">Closed issues: </p>
     3452      <h2 id="rfc.section.D.14"><a href="#rfc.section.D.14">D.14</a>&nbsp;<a id="changes.since.12" href="#changes.since.12">Since draft-ietf-httpbis-p1-messaging-12</a></h2>
     3453      <p id="rfc.section.D.14.p.1">Closed issues: </p>
    34533454      <ul>
    34543455         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/75">http://tools.ietf.org/wg/httpbis/trac/ticket/75</a>&gt;: "RFC2145 Normative"
     
    34693470         </li>
    34703471      </ul>
    3471       <h2 id="rfc.section.C.15"><a href="#rfc.section.C.15">C.15</a>&nbsp;<a id="changes.since.13" href="#changes.since.13">Since draft-ietf-httpbis-p1-messaging-13</a></h2>
    3472       <p id="rfc.section.C.15.p.1">Closed issues: </p>
     3472      <h2 id="rfc.section.D.15"><a href="#rfc.section.D.15">D.15</a>&nbsp;<a id="changes.since.13" href="#changes.since.13">Since draft-ietf-httpbis-p1-messaging-13</a></h2>
     3473      <p id="rfc.section.D.15.p.1">Closed issues: </p>
    34733474      <ul>
    34743475         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/53">http://tools.ietf.org/wg/httpbis/trac/ticket/53</a>&gt;: "Allow is not in 13.5.2"
     
    34813482         </li>
    34823483      </ul>
    3483       <h2 id="rfc.section.C.16"><a href="#rfc.section.C.16">C.16</a>&nbsp;<a id="changes.since.14" href="#changes.since.14">Since draft-ietf-httpbis-p1-messaging-14</a></h2>
    3484       <p id="rfc.section.C.16.p.1">Closed issues: </p>
     3484      <h2 id="rfc.section.D.16"><a href="#rfc.section.D.16">D.16</a>&nbsp;<a id="changes.since.14" href="#changes.since.14">Since draft-ietf-httpbis-p1-messaging-14</a></h2>
     3485      <p id="rfc.section.D.16.p.1">Closed issues: </p>
    34853486      <ul>
    34863487         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/273">http://tools.ietf.org/wg/httpbis/trac/ticket/273</a>&gt;: "HTTP-version should be redefined as fixed length pair of DIGIT . DIGIT"
     
    34933494         </li>
    34943495      </ul>
    3495       <h2 id="rfc.section.C.17"><a href="#rfc.section.C.17">C.17</a>&nbsp;<a id="changes.since.15" href="#changes.since.15">Since draft-ietf-httpbis-p1-messaging-15</a></h2>
    3496       <p id="rfc.section.C.17.p.1">Closed issues: </p>
     3496      <h2 id="rfc.section.D.17"><a href="#rfc.section.D.17">D.17</a>&nbsp;<a id="changes.since.15" href="#changes.since.15">Since draft-ietf-httpbis-p1-messaging-15</a></h2>
     3497      <p id="rfc.section.D.17.p.1">Closed issues: </p>
    34973498      <ul>
    34983499         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/100">http://tools.ietf.org/wg/httpbis/trac/ticket/100</a>&gt;: "DNS Spoofing / DNS Binding advice"
     
    35053506         </li>
    35063507      </ul>
    3507       <h2 id="rfc.section.C.18"><a href="#rfc.section.C.18">C.18</a>&nbsp;<a id="changes.since.16" href="#changes.since.16">Since draft-ietf-httpbis-p1-messaging-16</a></h2>
    3508       <p id="rfc.section.C.18.p.1">Closed issues: </p>
     3508      <h2 id="rfc.section.D.18"><a href="#rfc.section.D.18">D.18</a>&nbsp;<a id="changes.since.16" href="#changes.since.16">Since draft-ietf-httpbis-p1-messaging-16</a></h2>
     3509      <p id="rfc.section.D.18.p.1">Closed issues: </p>
    35093510      <ul>
    35103511         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/186">http://tools.ietf.org/wg/httpbis/trac/ticket/186</a>&gt;: "Document HTTP's error-handling philosophy"
     
    35193520         </li>
    35203521      </ul>
    3521       <h2 id="rfc.section.C.19"><a href="#rfc.section.C.19">C.19</a>&nbsp;<a id="changes.since.17" href="#changes.since.17">Since draft-ietf-httpbis-p1-messaging-17</a></h2>
    3522       <p id="rfc.section.C.19.p.1">Closed issues: </p>
     3522      <h2 id="rfc.section.D.19"><a href="#rfc.section.D.19">D.19</a>&nbsp;<a id="changes.since.17" href="#changes.since.17">Since draft-ietf-httpbis-p1-messaging-17</a></h2>
     3523      <p id="rfc.section.D.19.p.1">Closed issues: </p>
    35233524      <ul>
    35243525         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/158">http://tools.ietf.org/wg/httpbis/trac/ticket/158</a>&gt;: "Proxy-Connection and Keep-Alive"
     
    35333534         </li>
    35343535      </ul>
    3535       <h2 id="rfc.section.C.20"><a href="#rfc.section.C.20">C.20</a>&nbsp;<a id="changes.since.18" href="#changes.since.18">Since draft-ietf-httpbis-p1-messaging-18</a></h2>
    3536       <p id="rfc.section.C.20.p.1">Closed issues: </p>
     3536      <h2 id="rfc.section.D.20"><a href="#rfc.section.D.20">D.20</a>&nbsp;<a id="changes.since.18" href="#changes.since.18">Since draft-ietf-httpbis-p1-messaging-18</a></h2>
     3537      <p id="rfc.section.D.20.p.1">Closed issues: </p>
    35373538      <ul>
    35383539         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/250">http://tools.ietf.org/wg/httpbis/trac/ticket/250</a>&gt;: "message-body in CONNECT response"
     
    35473548         </li>
    35483549      </ul>
    3549       <h2 id="rfc.section.C.21"><a href="#rfc.section.C.21">C.21</a>&nbsp;<a id="changes.since.19" href="#changes.since.19">Since draft-ietf-httpbis-p1-messaging-19</a></h2>
    3550       <p id="rfc.section.C.21.p.1">Closed issues: </p>
     3550      <h2 id="rfc.section.D.21"><a href="#rfc.section.D.21">D.21</a>&nbsp;<a id="changes.since.19" href="#changes.since.19">Since draft-ietf-httpbis-p1-messaging-19</a></h2>
     3551      <p id="rfc.section.D.21.p.1">Closed issues: </p>
    35513552      <ul>
    35523553         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/346">http://tools.ietf.org/wg/httpbis/trac/ticket/346</a>&gt;: "make IANA policy definitions consistent"
     
    38403841                  <li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">1.1</a>, <a href="#RFC2119"><b>10.1</b></a></li>
    38413842                  <li><em>RFC2145</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2145.1">1</a>, <a href="#rfc.xref.RFC2145.2">9</a>, <a href="#RFC2145"><b>10.2</b></a></li>
    3842                   <li><em>RFC2616</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">1</a>, <a href="#rfc.xref.RFC2616.2">2.7</a>, <a href="#rfc.xref.RFC2616.3">5.6.2</a>, <a href="#rfc.xref.RFC2616.4">9</a>, <a href="#rfc.xref.RFC2616.5">9</a>, <a href="#RFC2616"><b>10.2</b></a>, <a href="#rfc.xref.RFC2616.6">C.1</a><ul>
     3843                  <li><em>RFC2616</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">1</a>, <a href="#rfc.xref.RFC2616.2">2.7</a>, <a href="#rfc.xref.RFC2616.3">5.6.2</a>, <a href="#rfc.xref.RFC2616.4">9</a>, <a href="#rfc.xref.RFC2616.5">9</a>, <a href="#RFC2616"><b>10.2</b></a>, <a href="#rfc.xref.RFC2616.6">D.1</a><ul>
    38433844                        <li><em>Section 14.15</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.3">5.6.2</a></li>
    38443845                        <li><em>Section 16</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.5">9</a></li>
     
    38763877                     </ul>
    38773878                  </li>
    3878                   <li><em>RFC5234</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.1">1.2</a>, <a href="#rfc.xref.RFC5234.2">1.2</a>, <a href="#rfc.xref.RFC5234.3">3.2.5</a>, <a href="#RFC5234"><b>10.1</b></a><ul>
     3879                  <li><em>RFC5234</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.1">1.2</a>, <a href="#rfc.xref.RFC5234.2">1.2</a>, <a href="#RFC5234"><b>10.1</b></a>, <a href="#rfc.xref.RFC5234.3">B</a><ul>
    38793880                        <li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.2">1.2</a></li>
    38803881                     </ul>
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r1792 r1798  
    14481448</section>
    14491449
    1450 <section title="ABNF list extension: #rule" anchor="abnf.extension">
    1451 <t>
    1452   A #rule extension to the ABNF rules of <xref target="RFC5234"/> is used to
    1453   improve readability in the definitions of some header field values.
    1454 </t>
    1455 <t>
    1456   A construct "#" is defined, similar to "*", for defining comma-delimited
    1457   lists of elements. The full form is "&lt;n&gt;#&lt;m&gt;element" indicating
    1458   at least &lt;n&gt; and at most &lt;m&gt; elements, each separated by a single
    1459   comma (",") and optional whitespace (OWS).   
    1460 </t>
    1461 <figure><preamble>
    1462   Thus,
    1463 </preamble><artwork type="example">
    1464   1#element =&gt; element *( OWS "," OWS element )
    1465 </artwork></figure>
    1466 <figure><preamble>
    1467   and:
    1468 </preamble><artwork type="example">
    1469   #element =&gt; [ 1#element ]
    1470 </artwork></figure>
    1471 <figure><preamble>
    1472   and for n &gt;= 1 and m &gt; 1:
    1473 </preamble><artwork type="example">
    1474   &lt;n&gt;#&lt;m&gt;element =&gt; element &lt;n-1&gt;*&lt;m-1&gt;( OWS "," OWS element )
    1475 </artwork></figure>
    1476 <t>
    1477   For compatibility with legacy list rules, recipients &SHOULD; accept empty
    1478   list elements. In other words, consumers would follow the list productions:
    1479 </t>
    1480 <figure><artwork type="example">
    1481   #element =&gt; [ ( "," / element ) *( OWS "," [ OWS element ] ) ]
    1482  
    1483   1#element =&gt; *( "," OWS ) element *( OWS "," [ OWS element ] )
    1484 </artwork></figure>
    1485 <t>
    1486   Note that empty elements do not contribute to the count of elements present,
    1487   though.
    1488 </t>
    1489 <t>
    1490   For example, given these ABNF productions:
    1491 </t>
    1492 <figure><artwork type="example">
    1493   example-list      = 1#example-list-elmt
    1494   example-list-elmt = token ; see <xref target="field.components"/>
    1495 </artwork></figure>
    1496 <t>
    1497   Then these are valid values for example-list (not including the double
    1498   quotes, which are present for delimitation only):
    1499 </t>
    1500 <figure><artwork type="example">
    1501   "foo,bar"
    1502   "foo ,bar,"
    1503   "foo , ,bar,charlie   "
    1504 </artwork></figure>
    1505 <t>
    1506   But these values would be invalid, as at least one non-empty element is
    1507   required:
    1508 </t>
    1509 <figure><artwork type="example">
    1510   ""
    1511   ","
    1512   ",   ,"
    1513 </artwork></figure>
    1514 <t>
    1515   <xref target="collected.abnf"/> shows the collected ABNF, with the list rules
    1516   expanded as explained above.
    1517 </t>
    1518 </section>
    15191450</section>
    15201451
     
    51025033</section>
    51035034
     5035<section title="ABNF list extension: #rule" anchor="abnf.extension">
     5036<t>
     5037  A #rule extension to the ABNF rules of <xref target="RFC5234"/> is used to
     5038  improve readability in the definitions of some header field values.
     5039</t>
     5040<t>
     5041  A construct "#" is defined, similar to "*", for defining comma-delimited
     5042  lists of elements. The full form is "&lt;n&gt;#&lt;m&gt;element" indicating
     5043  at least &lt;n&gt; and at most &lt;m&gt; elements, each separated by a single
     5044  comma (",") and optional whitespace (OWS).   
     5045</t>
     5046<figure><preamble>
     5047  Thus,
     5048</preamble><artwork type="example">
     5049  1#element =&gt; element *( OWS "," OWS element )
     5050</artwork></figure>
     5051<figure><preamble>
     5052  and:
     5053</preamble><artwork type="example">
     5054  #element =&gt; [ 1#element ]
     5055</artwork></figure>
     5056<figure><preamble>
     5057  and for n &gt;= 1 and m &gt; 1:
     5058</preamble><artwork type="example">
     5059  &lt;n&gt;#&lt;m&gt;element =&gt; element &lt;n-1&gt;*&lt;m-1&gt;( OWS "," OWS element )
     5060</artwork></figure>
     5061<t>
     5062  For compatibility with legacy list rules, recipients &SHOULD; accept empty
     5063  list elements. In other words, consumers would follow the list productions:
     5064</t>
     5065<figure><artwork type="example">
     5066  #element =&gt; [ ( "," / element ) *( OWS "," [ OWS element ] ) ]
     5067 
     5068  1#element =&gt; *( "," OWS ) element *( OWS "," [ OWS element ] )
     5069</artwork></figure>
     5070<t>
     5071  Note that empty elements do not contribute to the count of elements present,
     5072  though.
     5073</t>
     5074<t>
     5075  For example, given these ABNF productions:
     5076</t>
     5077<figure><artwork type="example">
     5078  example-list      = 1#example-list-elmt
     5079  example-list-elmt = token ; see <xref target="field.components"/>
     5080</artwork></figure>
     5081<t>
     5082  Then these are valid values for example-list (not including the double
     5083  quotes, which are present for delimitation only):
     5084</t>
     5085<figure><artwork type="example">
     5086  "foo,bar"
     5087  "foo ,bar,"
     5088  "foo , ,bar,charlie   "
     5089</artwork></figure>
     5090<t>
     5091  But these values would be invalid, as at least one non-empty element is
     5092  required:
     5093</t>
     5094<figure><artwork type="example">
     5095  ""
     5096  ","
     5097  ",   ,"
     5098</artwork></figure>
     5099<t>
     5100  <xref target="collected.abnf"/> shows the collected ABNF, with the list rules
     5101  expanded as explained above.
     5102</t>
     5103</section>
     5104
    51045105<?BEGININC p1-messaging.abnf-appendix ?>
    51055106<section xmlns:x="http://purl.org/net/xml2rfc/ext" title="Collected ABNF" anchor="collected.abnf">
  • draft-ietf-httpbis/latest/p2-semantics.html

    r1797 r1798  
    11601160         with "X-" if they are to be registered (either immediately or in the future).
    11611161      </p>
    1162       <p id="rfc.section.3.1.p.3">New header field values typically have their syntax defined using ABNF (<a href="#RFC5234" id="rfc.xref.RFC5234.3"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>), using the extension defined in <a href="p1-messaging.html#abnf.extension" title="ABNF list extension: #rule">Section 3.2.5</a> of <a href="#Part1" id="rfc.xref.Part1.23"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> as necessary, and are usually constrained to the range of ASCII characters. Header fields needing a greater range of characters
     1162      <p id="rfc.section.3.1.p.3">New header field values typically have their syntax defined using ABNF (<a href="#RFC5234" id="rfc.xref.RFC5234.3"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>), using the extension defined in <a href="p1-messaging.html#abnf.extension" title="ABNF list extension: #rule">Appendix B</a> of <a href="#Part1" id="rfc.xref.Part1.23"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> as necessary, and are usually constrained to the range of ASCII characters. Header fields needing a greater range of characters
    11631163         can use an encoding such as the one defined in <a href="#RFC5987" id="rfc.xref.RFC5987.1"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a>.
    11641164      </p>
     
    49334933                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.22">3</a>, <a href="#rfc.xref.Part1.25">3.1</a>, <a href="#rfc.xref.Part1.51">9.17</a>, <a href="#rfc.xref.Part1.53">9.18</a></li>
    49344934                        <li><em>Section 3.2.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.8">1.2.1</a>, <a href="#rfc.xref.Part1.9">1.2.1</a>, <a href="#rfc.xref.Part1.10">1.2.1</a>, <a href="#rfc.xref.Part1.12">1.2.2</a>, <a href="#rfc.xref.Part1.24">3.1</a></li>
    4935                         <li><em>Section 3.2.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.23">3.1</a></li>
    49364935                        <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.17">2.2.1</a>, <a href="#rfc.xref.Part1.34">4.4.6</a>, <a href="#rfc.xref.Part1.43">6.2</a>, <a href="#rfc.xref.Part1.44">7</a></li>
    49374936                        <li><em>Section 3.3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.42">6.1</a></li>
     
    49534952                        <li><em>Section 7.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.20">2.3.7</a></li>
    49544953                        <li><em>Section 9</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.57">12</a></li>
     4954                        <li><em>Appendix B</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.23">3.1</a></li>
    49554955                     </ul>
    49564956                  </li>
  • draft-ietf-httpbis/latest/p3-payload.html

    r1773 r1798  
    374374  }
    375375  @bottom-center {
    376        content: "Expires January 15, 2013";
     376       content: "Expires January 17, 2013";
    377377  }
    378378  @bottom-right {
     
    404404      <meta name="dct.creator" content="Reschke, J. F.">
    405405      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p3-payload-latest">
    406       <meta name="dct.issued" scheme="ISO8601" content="2012-07-14">
     406      <meta name="dct.issued" scheme="ISO8601" content="2012-07-16">
    407407      <meta name="dct.abstract" content="This part is now obsolete. Please see HTTPbis, Part 2.">
    408408      <meta name="description" content="This part is now obsolete. Please see HTTPbis, Part 2.">
     
    424424            </tr>
    425425            <tr>
    426                <td class="left">Expires: January 15, 2013</td>
     426               <td class="left">Expires: January 17, 2013</td>
    427427               <td class="right">W3C</td>
    428428            </tr>
     
    437437            <tr>
    438438               <td class="left"></td>
    439                <td class="right">July 14, 2012</td>
     439               <td class="right">July 16, 2012</td>
    440440            </tr>
    441441         </tbody>
     
    453453         in progress”.
    454454      </p>
    455       <p>This Internet-Draft will expire on January 15, 2013.</p>
     455      <p>This Internet-Draft will expire on January 17, 2013.</p>
    456456      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    457457      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
  • draft-ietf-httpbis/latest/p5-range.html

    r1776 r1798  
    449449  }
    450450  @bottom-center {
    451        content: "Expires January 15, 2013";
     451       content: "Expires January 17, 2013";
    452452  }
    453453  @bottom-right {
     
    492492      <meta name="dct.creator" content="Reschke, J. F.">
    493493      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest">
    494       <meta name="dct.issued" scheme="ISO8601" content="2012-07-14">
     494      <meta name="dct.issued" scheme="ISO8601" content="2012-07-16">
    495495      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    496496      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 5 defines range requests and the rules for constructing and combining responses to those requests.">
     
    518518            </tr>
    519519            <tr>
    520                <td class="left">Expires: January 15, 2013</td>
     520               <td class="left">Expires: January 17, 2013</td>
    521521               <td class="right">J. Reschke, Editor</td>
    522522            </tr>
     
    527527            <tr>
    528528               <td class="left"></td>
    529                <td class="right">July 14, 2012</td>
     529               <td class="right">July 16, 2012</td>
    530530            </tr>
    531531         </tbody>
     
    554554         in progress”.
    555555      </p>
    556       <p>This Internet-Draft will expire on January 15, 2013.</p>
     556      <p>This Internet-Draft will expire on January 17, 2013.</p>
    557557      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    558558      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
Note: See TracChangeset for help on using the changeset viewer.