Ignore:
Timestamp:
01/07/13 08:47:55 (7 years ago)
Author:
julian.reschke@…
Message:

bump up document dates; update to latest version of rfc2629.xslt

File:
1 edited

Legend:

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

    r2300 r2301  
    440440  }
    441441  @top-right {
    442        content: "June 2013";
     442       content: "July 2013";
    443443  }
    444444  @top-center {
     
    449449  }
    450450  @bottom-center {
    451        content: "Expires December 25, 2013";
     451       content: "Expires January 2, 2014";
    452452  }
    453453  @bottom-right {
     
    486486      <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D">
    487487      <link href="p2-semantics.html" rel="next">
    488       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.597, 2013/05/27 06:39:42, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     488      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.598, 2013/06/23 14:11:10, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    489489      <link rel="schema.dct" href="http://purl.org/dc/terms/">
    490490      <meta name="dct.creator" content="Fielding, R.">
    491491      <meta name="dct.creator" content="Reschke, J. F.">
    492492      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
    493       <meta name="dct.issued" scheme="ISO8601" content="2013-06-23">
     493      <meta name="dct.issued" scheme="ISO8601" content="2013-07-01">
    494494      <meta name="dct.replaces" content="urn:ietf:rfc:2145">
    495495      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
     
    520520            <tr>
    521521               <td class="left">Intended status: Standards Track</td>
    522                <td class="right">June 23, 2013</td>
     522               <td class="right">July 1, 2013</td>
    523523            </tr>
    524524            <tr>
    525                <td class="left">Expires: December 25, 2013</td>
     525               <td class="left">Expires: January 2, 2014</td>
    526526               <td class="right"></td>
    527527            </tr>
     
    551551         in progress”.
    552552      </p>
    553       <p>This Internet-Draft will expire on December 25, 2013.</p>
     553      <p>This Internet-Draft will expire on January 2, 2014.</p>
    554554      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    555555      <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    775775      </p>
    776776      <div id="core.rules">
    777          <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
     777         <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
    778778            (hexadecimal 0-9/A-F/a-f), HTAB (horizontal tab), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), and VCHAR
    779779            (any visible <a href="#USASCII" id="rfc.xref.USASCII.1"><cite title="Coded Character Set -- 7-bit American Standard Code for Information Interchange">[USASCII]</cite></a> character).
     
    876876         often based on dynamic configuration for load balancing.
    877877      </p>
    878       <p id="rfc.section.2.3.p.4"> <span id="rfc.iref.u.2"></span><span id="rfc.iref.d.1"></span> <span id="rfc.iref.i.2"></span><span id="rfc.iref.o.2"></span> We use the terms "<dfn>upstream</dfn>" and "<dfn>downstream</dfn>" to describe various requirements in relation to the directional flow of a message: all messages flow from upstream to downstream.
     878      <p id="rfc.section.2.3.p.4"><span id="rfc.iref.u.2"></span><span id="rfc.iref.d.1"></span> <span id="rfc.iref.i.2"></span><span id="rfc.iref.o.2"></span> We use the terms "<dfn>upstream</dfn>" and "<dfn>downstream</dfn>" to describe various requirements in relation to the directional flow of a message: all messages flow from upstream to downstream.
    879879         Likewise, we use the terms inbound and outbound to refer to directions in relation to the request path: "<dfn>inbound</dfn>" means toward the origin server and "<dfn>outbound</dfn>" means toward the user agent.
    880880      </p>
     
    885885         for the sake of security, annotation services, or shared caching.
    886886      </p>
    887       <p id="rfc.section.2.3.p.6"> <span id="rfc.iref.t.1"></span> <span id="rfc.iref.n.1"></span> An HTTP-to-HTTP proxy is called a "<dfn>transforming proxy</dfn>" if it is designed or configured to modify request or response messages in a semantically meaningful way (i.e., modifications,
     887      <p id="rfc.section.2.3.p.6"><span id="rfc.iref.t.1"></span> <span id="rfc.iref.n.1"></span> An HTTP-to-HTTP proxy is called a "<dfn>transforming proxy</dfn>" if it is designed or configured to modify request or response messages in a semantically meaningful way (i.e., modifications,
    888888         beyond those required by normal HTTP processing, that change the message in a way that would be significant to the original
    889889         sender or potentially significant to downstream recipients). For example, a transforming proxy might be acting as a shared
     
    893893         a given message, we use the term "<dfn>non-transforming proxy</dfn>" to target requirements that preserve HTTP message semantics. See <a href="p2-semantics.html#status.203" title="203 Non-Authoritative Information">Section 6.3.4</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a> and <a href="p6-cache.html#header.warning" title="Warning">Section 7.5</a> of <a href="#Part6" id="rfc.xref.Part6.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a> for status and warning codes related to transformations.
    894894      </p>
    895       <p id="rfc.section.2.3.p.7"><span id="rfc.iref.g.13"></span><span id="rfc.iref.r.4"></span>  <span id="rfc.iref.a.1"></span> A "<dfn>gateway</dfn>" (a.k.a., "<dfn>reverse proxy</dfn>") is an intermediary that acts as an origin server for the outbound connection, but translates received requests and forwards
     895      <p id="rfc.section.2.3.p.7"><span id="rfc.iref.g.13"></span><span id="rfc.iref.r.4"></span> <span id="rfc.iref.a.1"></span> A "<dfn>gateway</dfn>" (a.k.a., "<dfn>reverse proxy</dfn>") is an intermediary that acts as an origin server for the outbound connection, but translates received requests and forwards
    896896         them inbound to another server or servers. Gateways are often used to encapsulate legacy or untrusted information services,
    897897         to improve server performance through "<dfn>accelerator</dfn>" caching, and to enable partitioning or load balancing of HTTP services across multiple machines.
     
    907907         when Transport Layer Security (TLS, <a href="#RFC5246" id="rfc.xref.RFC5246.1"><cite title="The Transport Layer Security (TLS) Protocol Version 1.2">[RFC5246]</cite></a>) is used to establish confidential communication through a shared firewall proxy.
    908908      </p>
    909       <p id="rfc.section.2.3.p.10"><span id="rfc.iref.i.3"></span>  <span id="rfc.iref.t.3"></span> <span id="rfc.iref.c.3"></span> The above categories for intermediary only consider those acting as participants in the HTTP communication. There are also
     909      <p id="rfc.section.2.3.p.10"><span id="rfc.iref.i.3"></span> <span id="rfc.iref.t.3"></span> <span id="rfc.iref.c.3"></span> The above categories for intermediary only consider those acting as participants in the HTTP communication. There are also
    910910         intermediaries that can act on lower layers of the network protocol stack, filtering or redirecting HTTP traffic without the
    911911         knowledge or permission of message senders. Network intermediaries often introduce security flaws or interoperability problems
     
    12411241         of the combined field value; a proxy <em class="bcp14">MUST NOT</em> change the order of these field values when forwarding a message.
    12421242      </p>
    1243       <div class="note" id="rfc.section.3.2.2.p.4"> 
    1244          <p> <b>Note:</b> In practice, the "Set-Cookie" header field (<a href="#RFC6265" id="rfc.xref.RFC6265.2"><cite title="HTTP State Management Mechanism">[RFC6265]</cite></a>) often appears multiple times in a response message and does not use the list syntax, violating the above requirements on
     1243      <div class="note" id="rfc.section.3.2.2.p.4">
     1244         <p><b>Note:</b> In practice, the "Set-Cookie" header field (<a href="#RFC6265" id="rfc.xref.RFC6265.2"><cite title="HTTP State Management Mechanism">[RFC6265]</cite></a>) often appears multiple times in a response message and does not use the list syntax, violating the above requirements on
    12451245            multiple header fields with the same name. Since it cannot be combined into a single field-value, recipients ought to handle
    12461246            "Set-Cookie" as a special case while processing header fields. (See Appendix A.2.3 of <a href="#Kri2001" id="rfc.xref.Kri2001.1"><cite title="HTTP Cookies: Standards, Privacy, and Politics">[Kri2001]</cite></a> for details.)
     
    12671267      </div>
    12681268      <div id="rule.whitespace">
    1269          <p id="rfc.section.3.2.3.p.5">      </p>
     1269         <p id="rfc.section.3.2.3.p.5">   </p>
    12701270      </div>
    12711271      <div id="rfc.figure.u.19"></div><pre class="inline"><span id="rfc.iref.g.40"></span><span id="rfc.iref.g.41"></span><span id="rfc.iref.g.42"></span>  <a href="#rule.whitespace" class="smpl">OWS</a>            = *( <a href="#core.rules" class="smpl">SP</a> / <a href="#core.rules" class="smpl">HTAB</a> )
     
    13101310      <h3 id="rfc.section.3.2.6"><a href="#rfc.section.3.2.6">3.2.6</a>&nbsp;<a id="field.components" href="#field.components">Field value components</a></h3>
    13111311      <div id="rule.token.separators">
    1312          <p id="rfc.section.3.2.6.p.1">        Many HTTP header field values consist of words (token or quoted-string) separated by whitespace or special characters. These
     1312         <p id="rfc.section.3.2.6.p.1">    Many HTTP header field values consist of words (token or quoted-string) separated by whitespace or special characters. These
    13131313            special characters <em class="bcp14">MUST</em> be in a quoted string to be used within a parameter value (as defined in <a href="#transfer.codings" title="Transfer Codings">Section&nbsp;4</a>).
    13141314         </p>
     
    13271327                 / "]" / "?" / "=" / "{" / "}"
    13281328</pre><div id="rule.quoted-string">
    1329          <p id="rfc.section.3.2.6.p.3">      A string of text is parsed as a single word if it is quoted using double-quote marks.</p>
     1329         <p id="rfc.section.3.2.6.p.3">   A string of text is parsed as a single word if it is quoted using double-quote marks.</p>
    13301330      </div>
    13311331      <div id="rfc.figure.u.21"></div><pre class="inline"><span id="rfc.iref.g.47"></span><span id="rfc.iref.g.48"></span><span id="rfc.iref.g.49"></span>  <a href="#rule.quoted-string" class="smpl">quoted-string</a>  = <a href="#core.rules" class="smpl">DQUOTE</a> *( <a href="#rule.quoted-string" class="smpl">qdtext</a> / <a href="#rule.quoted-pair" class="smpl">quoted-pair</a> ) <a href="#core.rules" class="smpl">DQUOTE</a>
     
    13331333  <a href="#rule.quoted-string" class="smpl">obs-text</a>       = %x80-FF
    13341334</pre><div id="rule.quoted-pair">
    1335          <p id="rfc.section.3.2.6.p.5">  The backslash octet ("\") can be used as a single-octet quoting mechanism within quoted-string constructs:</p>
     1335         <p id="rfc.section.3.2.6.p.5"> The backslash octet ("\") can be used as a single-octet quoting mechanism within quoted-string constructs:</p>
    13361336      </div>
    13371337      <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.50"></span>  <a href="#rule.quoted-pair" class="smpl">quoted-pair</a>    = "\" ( <a href="#core.rules" class="smpl">HTAB</a> / <a href="#core.rules" class="smpl">SP</a> / <a href="#core.rules" class="smpl">VCHAR</a> / <a href="#rule.quoted-string" class="smpl">obs-text</a> )
     
    13421342      </p>
    13431343      <div id="rule.comment">
    1344          <p id="rfc.section.3.2.6.p.9">    Comments can be included in some HTTP header fields by surrounding the comment text with parentheses. Comments are only allowed
     1344         <p id="rfc.section.3.2.6.p.9">  Comments can be included in some HTTP header fields by surrounding the comment text with parentheses. Comments are only allowed
    13451345            in fields containing "comment" as part of their field value definition.
    13461346         </p>
     
    13491349  <a href="#rule.comment" class="smpl">ctext</a>          = <a href="#core.rules" class="smpl">HTAB</a> / <a href="#core.rules" class="smpl">SP</a> / %x21-27 / %x2A-5B / %x5D-7E / <a href="#rule.quoted-string" class="smpl">obs-text</a>
    13501350</pre><div id="rule.quoted-cpair">
    1351          <p id="rfc.section.3.2.6.p.11">  The backslash octet ("\") can be used as a single-octet quoting mechanism within comment constructs:</p>
     1351         <p id="rfc.section.3.2.6.p.11"> The backslash octet ("\") can be used as a single-octet quoting mechanism within comment constructs:</p>
    13521352      </div>
    13531353      <div id="rfc.figure.u.24"></div><pre class="inline"><span id="rfc.iref.g.53"></span>  <a href="#rule.quoted-cpair" class="smpl">quoted-cpair</a>   = "\" ( <a href="#core.rules" class="smpl">HTAB</a> / <a href="#core.rules" class="smpl">SP</a> / <a href="#core.rules" class="smpl">VCHAR</a> / <a href="#rule.quoted-string" class="smpl">obs-text</a> )
     
    14411441         that decimal value prior to determining the message body length.
    14421442      </p>
    1443       <div class="note" id="rfc.section.3.3.2.p.13"> 
    1444          <p> <b>Note:</b> HTTP's use of Content-Length for message framing differs significantly from the same field's use in MIME, where it is an optional
     1443      <div class="note" id="rfc.section.3.3.2.p.13">
     1444         <p><b>Note:</b> HTTP's use of Content-Length for message framing differs significantly from the same field's use in MIME, where it is an optional
    14451445            field used only within the "message/external-body" media-type.
    14461446         </p>
     
    14491449      <h3 id="rfc.section.3.3.3"><a href="#rfc.section.3.3.3">3.3.3</a>&nbsp;<a id="message.body.length" href="#message.body.length">Message Body Length</a></h3>
    14501450      <p id="rfc.section.3.3.3.p.1">The length of a message body is determined by one of the following (in order of precedence):</p>
    1451       <p id="rfc.section.3.3.3.p.2"> </p>
     1451      <p id="rfc.section.3.3.3.p.2"></p>
    14521452      <ol>
    14531453         <li>
     
    15571557  <a href="#transfer.codings" class="smpl">transfer-extension</a> = <a href="#rule.token.separators" class="smpl">token</a> *( <a href="#rule.whitespace" class="smpl">OWS</a> ";" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#rule.parameter" class="smpl">transfer-parameter</a> )
    15581558</pre><div id="rule.parameter">
    1559          <p id="rfc.section.4.p.3">      Parameters are in the form of attribute/value pairs.</p>
     1559         <p id="rfc.section.4.p.3">   Parameters are in the form of attribute/value pairs.</p>
    15601560      </div>
    15611561      <div id="rfc.figure.u.31"></div><pre class="inline"><span id="rfc.iref.g.59"></span><span id="rfc.iref.g.60"></span><span id="rfc.iref.g.61"></span><span id="rfc.iref.g.62"></span><span id="rfc.iref.g.63"></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>
     
    16531653      <p id="rfc.section.4.2.2.p.1">The "deflate" coding is a "zlib" data format <a href="#RFC1950" id="rfc.xref.RFC1950.1"><cite title="ZLIB Compressed Data Format Specification version 3.3">[RFC1950]</cite></a> containing a "deflate" compressed data stream <a href="#RFC1951" id="rfc.xref.RFC1951.1"><cite title="DEFLATE Compressed Data Format Specification version 1.3">[RFC1951]</cite></a> that uses a combination of the Lempel-Ziv (LZ77) compression algorithm and Huffman coding.
    16541654      </p>
    1655       <div class="note" id="rfc.section.4.2.2.p.2"> 
    1656          <p> <b>Note:</b> Some incorrect implementations send the "deflate" compressed data without the zlib wrapper.
     1655      <div class="note" id="rfc.section.4.2.2.p.2">
     1656         <p><b>Note:</b> Some incorrect implementations send the "deflate" compressed data without the zlib wrapper.
    16571657         </p>
    16581658      </div>
     
    17411741  <a href="#asterisk-form" class="smpl">asterisk-form</a>  = "*"
    17421742</pre><div id="origin-form">
    1743          <p id="rfc.section.5.3.p.3"><span id="rfc.iref.o.3"></span>  <b>origin-form</b>
     1743         <p id="rfc.section.5.3.p.3"><span id="rfc.iref.o.3"></span> <b>origin-form</b>
    17441744         </p>
    17451745      </div>
     
    17571757</pre><p id="rfc.section.5.3.p.9">followed by the remainder of the request message.</p>
    17581758      <div id="absolute-form">
    1759          <p id="rfc.section.5.3.p.10"><span id="rfc.iref.a.2"></span>  <b>absolute-form</b>
     1759         <p id="rfc.section.5.3.p.10"><span id="rfc.iref.a.2"></span> <b>absolute-form</b>
    17601760         </p>
    17611761      </div>
     
    17691769      </p>
    17701770      <div id="authority-form">
    1771          <p id="rfc.section.5.3.p.15"><span id="rfc.iref.a.3"></span>  <b>authority-form</b>
     1771         <p id="rfc.section.5.3.p.15"><span id="rfc.iref.a.3"></span> <b>authority-form</b>
    17721772         </p>
    17731773      </div>
     
    17761776      <div id="rfc.figure.u.41"></div><pre class="text2">CONNECT www.example.com:80 HTTP/1.1
    17771777</pre><div id="asterisk-form">
    1778          <p id="rfc.section.5.3.p.18"><span id="rfc.iref.a.4"></span>  <b>asterisk-form</b>
     1778         <p id="rfc.section.5.3.p.18"><span id="rfc.iref.a.4"></span> <b>asterisk-form</b>
    17791779         </p>
    17801780      </div>
     
    19961996</pre><p id="rfc.section.6.1.p.12">in either the request or the response header fields indicates that the connection <em class="bcp14">MUST</em> be closed after the current request/response is complete (<a href="#persistent.tear-down" id="rfc.xref.persistent.tear-down.1" title="Tear-down">Section&nbsp;6.6</a>).
    19971997      </p>
    1998       <p id="rfc.section.6.1.p.13">A client that does not support <a href="#persistent.connections" class="smpl">persistent connections</a>  <em class="bcp14">MUST</em> send the "close" connection option in every request message.
    1999       </p>
    2000       <p id="rfc.section.6.1.p.14">A server that does not support <a href="#persistent.connections" class="smpl">persistent connections</a>  <em class="bcp14">MUST</em> send the "close" connection option in every response message that does not have a <a href="p2-semantics.html#status.1xx" class="smpl">1xx (Informational)</a> status code.
     1998      <p id="rfc.section.6.1.p.13">A client that does not support <a href="#persistent.connections" class="smpl">persistent connections</a> <em class="bcp14">MUST</em> send the "close" connection option in every request message.
     1999      </p>
     2000      <p id="rfc.section.6.1.p.14">A server that does not support <a href="#persistent.connections" class="smpl">persistent connections</a> <em class="bcp14">MUST</em> send the "close" connection option in every response message that does not have a <a href="p2-semantics.html#status.1xx" class="smpl">1xx (Informational)</a> status code.
    20012001      </p>
    20022002      <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a>&nbsp;<a id="persistent.establishment" href="#persistent.establishment">Establishment</a></h2>
     
    21952195                  <td class="left">http</td>
    21962196                  <td class="left">standard</td>
    2197                   <td class="left"> <a href="#header.connection" id="rfc.xref.header.connection.7" title="Connection">Section&nbsp;6.1</a>
     2197                  <td class="left"><a href="#header.connection" id="rfc.xref.header.connection.7" title="Connection">Section&nbsp;6.1</a>
    21982198                  </td>
    21992199               </tr>
     
    22022202                  <td class="left">http</td>
    22032203                  <td class="left">standard</td>
    2204                   <td class="left"> <a href="#header.content-length" id="rfc.xref.header.content-length.1" title="Content-Length">Section&nbsp;3.3.2</a>
     2204                  <td class="left"><a href="#header.content-length" id="rfc.xref.header.content-length.1" title="Content-Length">Section&nbsp;3.3.2</a>
    22052205                  </td>
    22062206               </tr>
     
    22092209                  <td class="left">http</td>
    22102210                  <td class="left">standard</td>
    2211                   <td class="left"> <a href="#header.host" id="rfc.xref.header.host.2" title="Host">Section&nbsp;5.4</a>
     2211                  <td class="left"><a href="#header.host" id="rfc.xref.header.host.2" title="Host">Section&nbsp;5.4</a>
    22122212                  </td>
    22132213               </tr>
     
    22162216                  <td class="left">http</td>
    22172217                  <td class="left">standard</td>
    2218                   <td class="left"> <a href="#header.te" id="rfc.xref.header.te.3" title="TE">Section&nbsp;4.3</a>
     2218                  <td class="left"><a href="#header.te" id="rfc.xref.header.te.3" title="TE">Section&nbsp;4.3</a>
    22192219                  </td>
    22202220               </tr>
     
    22232223                  <td class="left">http</td>
    22242224                  <td class="left">standard</td>
    2225                   <td class="left"> <a href="#header.trailer" id="rfc.xref.header.trailer.1" title="Trailer">Section&nbsp;4.1.1</a>
     2225                  <td class="left"><a href="#header.trailer" id="rfc.xref.header.trailer.1" title="Trailer">Section&nbsp;4.1.1</a>
    22262226                  </td>
    22272227               </tr>
     
    22302230                  <td class="left">http</td>
    22312231                  <td class="left">standard</td>
    2232                   <td class="left"> <a href="#header.transfer-encoding" id="rfc.xref.header.transfer-encoding.3" title="Transfer-Encoding">Section&nbsp;3.3.1</a>
     2232                  <td class="left"><a href="#header.transfer-encoding" id="rfc.xref.header.transfer-encoding.3" title="Transfer-Encoding">Section&nbsp;3.3.1</a>
    22332233                  </td>
    22342234               </tr>
     
    22372237                  <td class="left">http</td>
    22382238                  <td class="left">standard</td>
    2239                   <td class="left"> <a href="#header.upgrade" id="rfc.xref.header.upgrade.2" title="Upgrade">Section&nbsp;6.7</a>
     2239                  <td class="left"><a href="#header.upgrade" id="rfc.xref.header.upgrade.2" title="Upgrade">Section&nbsp;6.7</a>
    22402240                  </td>
    22412241               </tr>
     
    22442244                  <td class="left">http</td>
    22452245                  <td class="left">standard</td>
    2246                   <td class="left"> <a href="#header.via" id="rfc.xref.header.via.1" title="Via">Section&nbsp;5.7.1</a>
     2246                  <td class="left"><a href="#header.via" id="rfc.xref.header.via.1" title="Via">Section&nbsp;5.7.1</a>
    22472247                  </td>
    22482248               </tr>
     
    22682268                  <td class="left">http</td>
    22692269                  <td class="left">reserved</td>
    2270                   <td class="left"> <a href="#header.field.registration" title="Header Field Registration">Section&nbsp;7.1</a>
     2270                  <td class="left"><a href="#header.field.registration" title="Header Field Registration">Section&nbsp;7.1</a>
    22712271                  </td>
    22722272               </tr>
     
    23142314         for all "message" types regarding line length and encodings.
    23152315      </p>
    2316       <p id="rfc.section.7.3.1.p.2"> </p>
     2316      <p id="rfc.section.7.3.1.p.2"></p>
    23172317      <dl>
    23182318         <dt>Type name:</dt>
     
    23442344         <dt>Applications that use this media type:</dt>
    23452345         <dt>Additional information:</dt>
    2346          <dd> 
     2346         <dd>
    23472347            <dl>
    23482348               <dt>Magic number(s):</dt>
     
    23692369      <h3 id="rfc.section.7.3.2"><a href="#rfc.section.7.3.2">7.3.2</a>&nbsp;<a id="internet.media.type.application.http" href="#internet.media.type.application.http">Internet Media Type application/http</a></h3>
    23702370      <p id="rfc.section.7.3.2.p.1">The application/http type can be used to enclose a pipeline of one or more HTTP request or response messages (not intermixed).</p>
    2371       <p id="rfc.section.7.3.2.p.2"> </p>
     2371      <p id="rfc.section.7.3.2.p.2"></p>
    23722372      <dl>
    23732373         <dt>Type name:</dt>
     
    24012401         <dt>Applications that use this media type:</dt>
    24022402         <dt>Additional information:</dt>
    2403          <dd> 
     2403         <dd>
    24042404            <dl>
    24052405               <dt>Magic number(s):</dt>
     
    24542454                  <td class="left">chunked</td>
    24552455                  <td class="left">Transfer in a series of chunks</td>
    2456                   <td class="left"> <a href="#chunked.encoding" title="Chunked Transfer Coding">Section&nbsp;4.1</a>
     2456                  <td class="left"><a href="#chunked.encoding" title="Chunked Transfer Coding">Section&nbsp;4.1</a>
    24572457                  </td>
    24582458               </tr>
     
    24602460                  <td class="left">compress</td>
    24612461                  <td class="left">UNIX "compress" data format <a href="#Welch" id="rfc.xref.Welch.2"><cite title="A Technique for High Performance Data Compression">[Welch]</cite></a></td>
    2462                   <td class="left"> <a href="#compress.coding" title="Compress Coding">Section&nbsp;4.2.1</a>
     2462                  <td class="left"><a href="#compress.coding" title="Compress Coding">Section&nbsp;4.2.1</a>
    24632463                  </td>
    24642464               </tr>
     
    24672467                  <td class="left">"deflate" compressed data (<a href="#RFC1951" id="rfc.xref.RFC1951.2"><cite title="DEFLATE Compressed Data Format Specification version 1.3">[RFC1951]</cite></a>) inside the "zlib" data format (<a href="#RFC1950" id="rfc.xref.RFC1950.2"><cite title="ZLIB Compressed Data Format Specification version 3.3">[RFC1950]</cite></a>)
    24682468                  </td>
    2469                   <td class="left"> <a href="#deflate.coding" title="Deflate Coding">Section&nbsp;4.2.2</a>
     2469                  <td class="left"><a href="#deflate.coding" title="Deflate Coding">Section&nbsp;4.2.2</a>
    24702470                  </td>
    24712471               </tr>
     
    24732473                  <td class="left">gzip</td>
    24742474                  <td class="left">GZIP file format <a href="#RFC1952" id="rfc.xref.RFC1952.2"><cite title="GZIP file format specification version 4.3">[RFC1952]</cite></a></td>
    2475                   <td class="left"> <a href="#gzip.coding" title="Gzip Coding">Section&nbsp;4.2.3</a>
     2475                  <td class="left"><a href="#gzip.coding" title="Gzip Coding">Section&nbsp;4.2.3</a>
    24762476                  </td>
    24772477               </tr>
     
    24792479                  <td class="left">x-compress</td>
    24802480                  <td class="left">Deprecated (alias for compress)</td>
    2481                   <td class="left"> <a href="#compress.coding" title="Compress Coding">Section&nbsp;4.2.1</a>
     2481                  <td class="left"><a href="#compress.coding" title="Compress Coding">Section&nbsp;4.2.1</a>
    24822482                  </td>
    24832483               </tr>
     
    24852485                  <td class="left">x-gzip</td>
    24862486                  <td class="left">Deprecated (alias for gzip)</td>
    2487                   <td class="left"> <a href="#gzip.coding" title="Gzip Coding">Section&nbsp;4.2.3</a>
     2487                  <td class="left"><a href="#gzip.coding" title="Gzip Coding">Section&nbsp;4.2.3</a>
    24882488                  </td>
    24892489               </tr>
     
    26572657         <tr>
    26582658            <td class="reference"><b id="Part2">[Part2]</b></td>
    2659             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-latest (work in progress), June&nbsp;2013.
     2659            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-latest (work in progress), July&nbsp;2013.
    26602660            </td>
    26612661         </tr>
    26622662         <tr>
    26632663            <td class="reference"><b id="Part4">[Part4]</b></td>
    2664             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-latest (work in progress), June&nbsp;2013.
     2664            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-latest (work in progress), July&nbsp;2013.
    26652665            </td>
    26662666         </tr>
    26672667         <tr>
    26682668            <td class="reference"><b id="Part5">[Part5]</b></td>
    2669             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">Hypertext Transfer Protocol (HTTP/1.1): Range Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-latest (work in progress), June&nbsp;2013.
     2669            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">Hypertext Transfer Protocol (HTTP/1.1): Range Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-latest (work in progress), July&nbsp;2013.
    26702670            </td>
    26712671         </tr>
    26722672         <tr>
    26732673            <td class="reference"><b id="Part6">[Part6]</b></td>
    2674             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), June&nbsp;2013.
     2674            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), July&nbsp;2013.
    26752675            </td>
    26762676         </tr>
    26772677         <tr>
    26782678            <td class="reference"><b id="Part7">[Part7]</b></td>
    2679             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">Hypertext Transfer Protocol (HTTP/1.1): Authentication</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p7-auth-latest (work in progress), June&nbsp;2013.
     2679            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">Hypertext Transfer Protocol (HTTP/1.1): Authentication</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p7-auth-latest (work in progress), July&nbsp;2013.
    26802680            </td>
    26812681         </tr>
     
    30143014  ","
    30153015  ",   ,"
    3016 </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.
     3016</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.
    30173017      </p>
    30183018      <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
     
    31473147      <p id="rfc.section.D.2.p.1">Closed issues: </p>
    31483148      <ul>
    3149          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/128">http://tools.ietf.org/wg/httpbis/trac/ticket/128</a>&gt;: "Cite HTTPS URI scheme definition" (the spec now includes the HTTPs scheme definition and thus updates RFC 2818)
    3150          </li>
    3151          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/389">http://tools.ietf.org/wg/httpbis/trac/ticket/389</a>&gt;: "mention of 'proxies' in section about caches"
    3152          </li>
    3153          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/390">http://tools.ietf.org/wg/httpbis/trac/ticket/390</a>&gt;: "use of ABNF terms from RFC 3986"
    3154          </li>
    3155          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/391">http://tools.ietf.org/wg/httpbis/trac/ticket/391</a>&gt;: "transferring URIs with userinfo in payload"
    3156          </li>
    3157          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/392">http://tools.ietf.org/wg/httpbis/trac/ticket/392</a>&gt;: "editorial improvements to message length definition"
    3158          </li>
    3159          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/395">http://tools.ietf.org/wg/httpbis/trac/ticket/395</a>&gt;: "Connection header field MUST vs SHOULD"
    3160          </li>
    3161          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/396">http://tools.ietf.org/wg/httpbis/trac/ticket/396</a>&gt;: "editorial improvements to persistent connections section"
    3162          </li>
    3163          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/397">http://tools.ietf.org/wg/httpbis/trac/ticket/397</a>&gt;: "URI normalization vs empty path"
    3164          </li>
    3165          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/408">http://tools.ietf.org/wg/httpbis/trac/ticket/408</a>&gt;: "p1 feedback"
    3166          </li>
    3167          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/409">http://tools.ietf.org/wg/httpbis/trac/ticket/409</a>&gt;: "is parsing OBS-FOLD mandatory?"
    3168          </li>
    3169          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/410">http://tools.ietf.org/wg/httpbis/trac/ticket/410</a>&gt;: "HTTPS and Shared Caching"
    3170          </li>
    3171          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/411">http://tools.ietf.org/wg/httpbis/trac/ticket/411</a>&gt;: "Requirements for recipients of ws between start-line and first header field"
    3172          </li>
    3173          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/412">http://tools.ietf.org/wg/httpbis/trac/ticket/412</a>&gt;: "SP and HT when being tolerant"
    3174          </li>
    3175          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/414">http://tools.ietf.org/wg/httpbis/trac/ticket/414</a>&gt;: "Message Parsing Strictness"
    3176          </li>
    3177          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/415">http://tools.ietf.org/wg/httpbis/trac/ticket/415</a>&gt;: "'Render'"
    3178          </li>
    3179          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/418">http://tools.ietf.org/wg/httpbis/trac/ticket/418</a>&gt;: "No-Transform"
    3180          </li>
    3181          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/419">http://tools.ietf.org/wg/httpbis/trac/ticket/419</a>&gt;: "p2 editorial feedback"
    3182          </li>
    3183          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/420">http://tools.ietf.org/wg/httpbis/trac/ticket/420</a>&gt;: "Content-Length SHOULD be sent"
    3184          </li>
    3185          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/431">http://tools.ietf.org/wg/httpbis/trac/ticket/431</a>&gt;: "origin-form does not allow path starting with "//""
    3186          </li>
    3187          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/433">http://tools.ietf.org/wg/httpbis/trac/ticket/433</a>&gt;: "ambiguity in part 1 example"
     3149         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/128">http://tools.ietf.org/wg/httpbis/trac/ticket/128</a>&gt;: "Cite HTTPS URI scheme definition" (the spec now includes the HTTPs scheme definition and thus updates RFC 2818)
     3150         </li>
     3151         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/389">http://tools.ietf.org/wg/httpbis/trac/ticket/389</a>&gt;: "mention of 'proxies' in section about caches"
     3152         </li>
     3153         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/390">http://tools.ietf.org/wg/httpbis/trac/ticket/390</a>&gt;: "use of ABNF terms from RFC 3986"
     3154         </li>
     3155         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/391">http://tools.ietf.org/wg/httpbis/trac/ticket/391</a>&gt;: "transferring URIs with userinfo in payload"
     3156         </li>
     3157         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/392">http://tools.ietf.org/wg/httpbis/trac/ticket/392</a>&gt;: "editorial improvements to message length definition"
     3158         </li>
     3159         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/395">http://tools.ietf.org/wg/httpbis/trac/ticket/395</a>&gt;: "Connection header field MUST vs SHOULD"
     3160         </li>
     3161         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/396">http://tools.ietf.org/wg/httpbis/trac/ticket/396</a>&gt;: "editorial improvements to persistent connections section"
     3162         </li>
     3163         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/397">http://tools.ietf.org/wg/httpbis/trac/ticket/397</a>&gt;: "URI normalization vs empty path"
     3164         </li>
     3165         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/408">http://tools.ietf.org/wg/httpbis/trac/ticket/408</a>&gt;: "p1 feedback"
     3166         </li>
     3167         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/409">http://tools.ietf.org/wg/httpbis/trac/ticket/409</a>&gt;: "is parsing OBS-FOLD mandatory?"
     3168         </li>
     3169         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/410">http://tools.ietf.org/wg/httpbis/trac/ticket/410</a>&gt;: "HTTPS and Shared Caching"
     3170         </li>
     3171         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/411">http://tools.ietf.org/wg/httpbis/trac/ticket/411</a>&gt;: "Requirements for recipients of ws between start-line and first header field"
     3172         </li>
     3173         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/412">http://tools.ietf.org/wg/httpbis/trac/ticket/412</a>&gt;: "SP and HT when being tolerant"
     3174         </li>
     3175         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/414">http://tools.ietf.org/wg/httpbis/trac/ticket/414</a>&gt;: "Message Parsing Strictness"
     3176         </li>
     3177         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/415">http://tools.ietf.org/wg/httpbis/trac/ticket/415</a>&gt;: "'Render'"
     3178         </li>
     3179         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/418">http://tools.ietf.org/wg/httpbis/trac/ticket/418</a>&gt;: "No-Transform"
     3180         </li>
     3181         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/419">http://tools.ietf.org/wg/httpbis/trac/ticket/419</a>&gt;: "p2 editorial feedback"
     3182         </li>
     3183         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/420">http://tools.ietf.org/wg/httpbis/trac/ticket/420</a>&gt;: "Content-Length SHOULD be sent"
     3184         </li>
     3185         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/431">http://tools.ietf.org/wg/httpbis/trac/ticket/431</a>&gt;: "origin-form does not allow path starting with "//""
     3186         </li>
     3187         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/433">http://tools.ietf.org/wg/httpbis/trac/ticket/433</a>&gt;: "ambiguity in part 1 example"
    31883188         </li>
    31893189      </ul>
     
    31913191      <p id="rfc.section.D.3.p.1">Closed issues: </p>
    31923192      <ul>
    3193          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/435">http://tools.ietf.org/wg/httpbis/trac/ticket/435</a>&gt;: "Part1 should have a reference to TCP (RFC 793)"
    3194          </li>
    3195          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/438">http://tools.ietf.org/wg/httpbis/trac/ticket/438</a>&gt;: "media type registration template issues"
    3196          </li>
    3197          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/442">http://tools.ietf.org/wg/httpbis/trac/ticket/442</a>&gt;: "BWS" (vs conformance)
    3198          </li>
    3199          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/444">http://tools.ietf.org/wg/httpbis/trac/ticket/444</a>&gt;: "obs-fold language"
    3200          </li>
    3201          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/445">http://tools.ietf.org/wg/httpbis/trac/ticket/445</a>&gt;: "Ordering in Upgrade"
    3202          </li>
    3203          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/446">http://tools.ietf.org/wg/httpbis/trac/ticket/446</a>&gt;: "p1 editorial feedback"
    3204          </li>
    3205          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/447">http://tools.ietf.org/wg/httpbis/trac/ticket/447</a>&gt;: "HTTP and TCP name delegation"
    3206          </li>
    3207          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/449">http://tools.ietf.org/wg/httpbis/trac/ticket/449</a>&gt;: "Receiving a higher minor HTTP version number"
    3208          </li>
    3209          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/451">http://tools.ietf.org/wg/httpbis/trac/ticket/451</a>&gt;: "HTTP(S) URIs and fragids"
    3210          </li>
    3211          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/457">http://tools.ietf.org/wg/httpbis/trac/ticket/457</a>&gt;: "Registering x-gzip and x-deflate"
    3212          </li>
    3213          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/460">http://tools.ietf.org/wg/httpbis/trac/ticket/460</a>&gt;: "Via and gateways"
    3214          </li>
    3215          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/465">http://tools.ietf.org/wg/httpbis/trac/ticket/465</a>&gt;: "Mention 203 Non-Authoritative Information in p1"
    3216          </li>
    3217          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/476">http://tools.ietf.org/wg/httpbis/trac/ticket/476</a>&gt;: "SHOULD and conformance"
    3218          </li>
    3219          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/477">http://tools.ietf.org/wg/httpbis/trac/ticket/477</a>&gt;: "Pipelining language"
    3220          </li>
    3221          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/482">http://tools.ietf.org/wg/httpbis/trac/ticket/482</a>&gt;: "proxy handling of a really bad Content-Length"
     3193         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/435">http://tools.ietf.org/wg/httpbis/trac/ticket/435</a>&gt;: "Part1 should have a reference to TCP (RFC 793)"
     3194         </li>
     3195         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/438">http://tools.ietf.org/wg/httpbis/trac/ticket/438</a>&gt;: "media type registration template issues"
     3196         </li>
     3197         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/442">http://tools.ietf.org/wg/httpbis/trac/ticket/442</a>&gt;: "BWS" (vs conformance)
     3198         </li>
     3199         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/444">http://tools.ietf.org/wg/httpbis/trac/ticket/444</a>&gt;: "obs-fold language"
     3200         </li>
     3201         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/445">http://tools.ietf.org/wg/httpbis/trac/ticket/445</a>&gt;: "Ordering in Upgrade"
     3202         </li>
     3203         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/446">http://tools.ietf.org/wg/httpbis/trac/ticket/446</a>&gt;: "p1 editorial feedback"
     3204         </li>
     3205         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/447">http://tools.ietf.org/wg/httpbis/trac/ticket/447</a>&gt;: "HTTP and TCP name delegation"
     3206         </li>
     3207         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/449">http://tools.ietf.org/wg/httpbis/trac/ticket/449</a>&gt;: "Receiving a higher minor HTTP version number"
     3208         </li>
     3209         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/451">http://tools.ietf.org/wg/httpbis/trac/ticket/451</a>&gt;: "HTTP(S) URIs and fragids"
     3210         </li>
     3211         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/457">http://tools.ietf.org/wg/httpbis/trac/ticket/457</a>&gt;: "Registering x-gzip and x-deflate"
     3212         </li>
     3213         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/460">http://tools.ietf.org/wg/httpbis/trac/ticket/460</a>&gt;: "Via and gateways"
     3214         </li>
     3215         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/465">http://tools.ietf.org/wg/httpbis/trac/ticket/465</a>&gt;: "Mention 203 Non-Authoritative Information in p1"
     3216         </li>
     3217         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/476">http://tools.ietf.org/wg/httpbis/trac/ticket/476</a>&gt;: "SHOULD and conformance"
     3218         </li>
     3219         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/477">http://tools.ietf.org/wg/httpbis/trac/ticket/477</a>&gt;: "Pipelining language"
     3220         </li>
     3221         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/482">http://tools.ietf.org/wg/httpbis/trac/ticket/482</a>&gt;: "proxy handling of a really bad Content-Length"
    32223222         </li>
    32233223      </ul>
Note: See TracChangeset for help on using the changeset viewer.