Ignore:
Timestamp:
Jul 29, 2008, 11:51:31 AM (11 years ago)
Author:
julian.reschke@…
Message:

Resolve #97: Move media type registrations into IANA considerations section (closes #97).

File:
1 edited

Legend:

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

    r290 r296  
    376376      <link rel="Chapter" title="11 Acknowledgments" href="#rfc.section.11">
    377377      <link rel="Chapter" href="#rfc.section.12" title="12 References">
    378       <link rel="Appendix" title="A Internet Media Types" href="#rfc.section.A">
    379       <link rel="Appendix" title="B Tolerant Applications" href="#rfc.section.B">
    380       <link rel="Appendix" title="C Conversion of Date Formats" href="#rfc.section.C">
    381       <link rel="Appendix" title="D Compatibility with Previous Versions" href="#rfc.section.D">
    382       <link rel="Appendix" title="E Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.E">
     378      <link rel="Appendix" title="A Tolerant Applications" href="#rfc.section.A">
     379      <link rel="Appendix" title="B Conversion of Date Formats" href="#rfc.section.B">
     380      <link rel="Appendix" title="C Compatibility with Previous Versions" href="#rfc.section.C">
     381      <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D">
    383382      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.384, 2008-07-18 10:33:47, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    384383      <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
     
    477476         <tr>
    478477            <td class="header left"></td>
    479             <td class="header right">July 19, 2008</td>
     478            <td class="header right">July 29, 2008</td>
    480479         </tr>
    481480      </table>
     
    510509         list is at &lt;<a href="http://www.tools.ietf.org/wg/httpbis/trac/report/11">http://www.tools.ietf.org/wg/httpbis/trac/report/11</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://www.tools.ietf.org/wg/httpbis/">http://www.tools.ietf.org/wg/httpbis/</a>&gt;.
    511510      </p> 
    512       <p>The changes in this draft are summarized in <a href="#changes.since.02" title="Since draft-ietf-httpbis-p1-messaging-02">Appendix&nbsp;E.4</a>.
     511      <p>The changes in this draft are summarized in <a href="#changes.since.02" title="Since draft-ietf-httpbis-p1-messaging-02">Appendix&nbsp;D.4</a>.
    513512      </p>
    514513      <hr class="noprint">
     
    609608         <li class="tocline0">9.&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul class="toc">
    610609               <li class="tocline1">9.1&nbsp;&nbsp;&nbsp;<a href="#message.header.registration">Message Header Registration</a></li>
     610               <li class="tocline1">9.2&nbsp;&nbsp;&nbsp;<a href="#internet.media.type.http">Internet Media Type Registrations</a><ul class="toc">
     611                     <li class="tocline1">9.2.1&nbsp;&nbsp;&nbsp;<a href="#internet.media.type.message.http">Internet Media Type message/http</a></li>
     612                     <li class="tocline1">9.2.2&nbsp;&nbsp;&nbsp;<a href="#internet.media.type.application.http">Internet Media Type application/http</a></li>
     613                  </ul>
     614               </li>
    611615            </ul>
    612616         </li>
     
    627631         </li>
    628632         <li class="tocline0"><a href="#rfc.authors">Authors' Addresses</a></li>
    629          <li class="tocline0">A.&nbsp;&nbsp;&nbsp;<a href="#internet.media.type.http">Internet Media Types</a><ul class="toc">
    630                <li class="tocline1">A.1&nbsp;&nbsp;&nbsp;<a href="#internet.media.type.message.http">Internet Media Type message/http</a></li>
    631                <li class="tocline1">A.2&nbsp;&nbsp;&nbsp;<a href="#internet.media.type.application.http">Internet Media Type application/http</a></li>
    632             </ul>
    633          </li>
    634          <li class="tocline0">B.&nbsp;&nbsp;&nbsp;<a href="#tolerant.applications">Tolerant Applications</a></li>
    635          <li class="tocline0">C.&nbsp;&nbsp;&nbsp;<a href="#conversion.of.date.formats">Conversion of Date Formats</a></li>
    636          <li class="tocline0">D.&nbsp;&nbsp;&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a><ul class="toc">
    637                <li class="tocline1">D.1&nbsp;&nbsp;&nbsp;<a href="#changes.from.1.0">Changes from HTTP/1.0</a><ul class="toc">
    638                      <li class="tocline1">D.1.1&nbsp;&nbsp;&nbsp;<a href="#changes.to.simplify.multi-homed.web.servers.and.conserve.ip.addresses">Changes to Simplify Multi-homed Web Servers and Conserve IP Addresses</a></li>
     633         <li class="tocline0">A.&nbsp;&nbsp;&nbsp;<a href="#tolerant.applications">Tolerant Applications</a></li>
     634         <li class="tocline0">B.&nbsp;&nbsp;&nbsp;<a href="#conversion.of.date.formats">Conversion of Date Formats</a></li>
     635         <li class="tocline0">C.&nbsp;&nbsp;&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a><ul class="toc">
     636               <li class="tocline1">C.1&nbsp;&nbsp;&nbsp;<a href="#changes.from.1.0">Changes from HTTP/1.0</a><ul class="toc">
     637                     <li class="tocline1">C.1.1&nbsp;&nbsp;&nbsp;<a href="#changes.to.simplify.multi-homed.web.servers.and.conserve.ip.addresses">Changes to Simplify Multi-homed Web Servers and Conserve IP Addresses</a></li>
    639638                  </ul>
    640639               </li>
    641                <li class="tocline1">D.2&nbsp;&nbsp;&nbsp;<a href="#compatibility.with.http.1.0.persistent.connections">Compatibility with HTTP/1.0 Persistent Connections</a></li>
    642                <li class="tocline1">D.3&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li>
    643                <li class="tocline1">D.4&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
     640               <li class="tocline1">C.2&nbsp;&nbsp;&nbsp;<a href="#compatibility.with.http.1.0.persistent.connections">Compatibility with HTTP/1.0 Persistent Connections</a></li>
     641               <li class="tocline1">C.3&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li>
     642               <li class="tocline1">C.4&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
    644643            </ul>
    645644         </li>
    646          <li class="tocline0">E.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc">
    647                <li class="tocline1">E.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.1">Since RFC2616</a></li>
    648                <li class="tocline1">E.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.2">Since draft-ietf-httpbis-p1-messaging-00</a></li>
    649                <li class="tocline1">E.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.3">Since draft-ietf-httpbis-p1-messaging-01</a></li>
    650                <li class="tocline1">E.4&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p1-messaging-02</a></li>
    651                <li class="tocline1">E.5&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p1-messaging-03</a></li>
     645         <li class="tocline0">D.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc">
     646               <li class="tocline1">D.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.1">Since RFC2616</a></li>
     647               <li class="tocline1">D.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.2">Since draft-ietf-httpbis-p1-messaging-00</a></li>
     648               <li class="tocline1">D.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.3">Since draft-ietf-httpbis-p1-messaging-01</a></li>
     649               <li class="tocline1">D.4&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p1-messaging-02</a></li>
     650               <li class="tocline1">D.5&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p1-messaging-03</a></li>
    652651            </ul>
    653652         </li>
     
    989988                   ; US-ASCII double-quote mark (34)
    990989</pre><div id="rule.CRLF">
    991          <p id="rfc.section.2.2.p.3">  HTTP/1.1 defines the sequence CR LF as the end-of-line marker for all protocol elements except the entity-body (see <a href="#tolerant.applications" title="Tolerant Applications">Appendix&nbsp;B</a> for tolerant applications). The end-of-line marker within an entity-body is defined by its associated media type, as described
     990         <p id="rfc.section.2.2.p.3">  HTTP/1.1 defines the sequence CR LF as the end-of-line marker for all protocol elements except the entity-body (see <a href="#tolerant.applications" title="Tolerant Applications">Appendix&nbsp;A</a> for tolerant applications). The end-of-line marker within an entity-body is defined by its associated media type, as described
    992991            in <a href="p3-payload.html#media.types" title="Media Types">Section 3.3</a> of <a href="#Part3" id="rfc.xref.Part3.5"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>.
    993992         </p>
     
    11521151   Sun Nov  6 08:49:37 1994       ; ANSI C's asctime() format
    11531152</pre><p id="rfc.section.3.3.1.p.3">The first format is preferred as an Internet standard and represents a fixed-length subset of that defined by <a href="#RFC1123" id="rfc.xref.RFC1123.1"><cite title="Requirements for Internet Hosts - Application and Support">[RFC1123]</cite></a> (an update to <a href="#RFC822" id="rfc.xref.RFC822.1"><cite title="Standard for the format of ARPA Internet text messages">[RFC822]</cite></a>). The other formats are described here only for compatibility with obsolete implementations. HTTP/1.1 clients and servers
    1154          that parse the date value <em class="bcp14">MUST</em> accept all three formats (for compatibility with HTTP/1.0), though they <em class="bcp14">MUST</em> only generate the RFC 1123 format for representing HTTP-date values in header fields. See <a href="#tolerant.applications" title="Tolerant Applications">Appendix&nbsp;B</a> for further information.
     1153         that parse the date value <em class="bcp14">MUST</em> accept all three formats (for compatibility with HTTP/1.0), though they <em class="bcp14">MUST</em> only generate the RFC 1123 format for representing HTTP-date values in header fields. See <a href="#tolerant.applications" title="Tolerant Applications">Appendix&nbsp;A</a> for further information.
    11551154      </p>
    11561155      <dl class="empty">
     
    15131512      <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<a id="the.resource.identified.by.a.request" href="#the.resource.identified.by.a.request">The Resource Identified by a Request</a></h2>
    15141513      <p id="rfc.section.5.2.p.1">The exact resource identified by an Internet request is determined by examining both the Request-URI and the Host header field.</p>
    1515       <p id="rfc.section.5.2.p.2">An origin server that does not allow resources to differ by the requested host <em class="bcp14">MAY</em> ignore the Host header field value when determining the resource identified by an HTTP/1.1 request. (But see <a href="#changes.to.simplify.multi-homed.web.servers.and.conserve.ip.addresses" title="Changes to Simplify Multi-homed Web Servers and Conserve IP Addresses">Appendix&nbsp;D.1.1</a> for other requirements on Host support in HTTP/1.1.)
     1514      <p id="rfc.section.5.2.p.2">An origin server that does not allow resources to differ by the requested host <em class="bcp14">MAY</em> ignore the Host header field value when determining the resource identified by an HTTP/1.1 request. (But see <a href="#changes.to.simplify.multi-homed.web.servers.and.conserve.ip.addresses" title="Changes to Simplify Multi-homed Web Servers and Conserve IP Addresses">Appendix&nbsp;C.1.1</a> for other requirements on Host support in HTTP/1.1.)
    15161515      </p>
    15171516      <p id="rfc.section.5.2.p.3">An origin server that does differentiate resources based on the host requested (sometimes referred to as virtual hosts or
     
    16071606         connection.
    16081607      </p>
    1609       <p id="rfc.section.7.1.2.1.p.4">Clients and servers <em class="bcp14">SHOULD NOT</em> assume that a persistent connection is maintained for HTTP versions less than 1.1 unless it is explicitly signaled. See <a href="#compatibility.with.http.1.0.persistent.connections" title="Compatibility with HTTP/1.0 Persistent Connections">Appendix&nbsp;D.2</a> for more information on backward compatibility with HTTP/1.0 clients.
     1608      <p id="rfc.section.7.1.2.1.p.4">Clients and servers <em class="bcp14">SHOULD NOT</em> assume that a persistent connection is maintained for HTTP versions less than 1.1 unless it is explicitly signaled. See <a href="#compatibility.with.http.1.0.persistent.connections" title="Compatibility with HTTP/1.0 Persistent Connections">Appendix&nbsp;C.2</a> for more information on backward compatibility with HTTP/1.0 clients.
    16101609      </p>
    16111610      <p id="rfc.section.7.1.2.1.p.5">In order to remain persistent, all messages on the connection <em class="bcp14">MUST</em> have a self-defined message length (i.e., one not defined by closure of the connection), as described in <a href="#message.length" title="Message Length">Section&nbsp;4.4</a>.
     
    17711770      </p>
    17721771      <p id="rfc.section.8.1.p.11">A system receiving an HTTP/1.0 (or lower-version) message that includes a Connection header <em class="bcp14">MUST</em>, for each connection-token in this field, remove and ignore any header field(s) from the message with the same name as the
    1773          connection-token. This protects against mistaken forwarding of such header fields by pre-HTTP/1.1 proxies. See <a href="#compatibility.with.http.1.0.persistent.connections" title="Compatibility with HTTP/1.0 Persistent Connections">Appendix&nbsp;D.2</a>.
     1772         connection-token. This protects against mistaken forwarding of such header fields by pre-HTTP/1.1 proxies. See <a href="#compatibility.with.http.1.0.persistent.connections" title="Compatibility with HTTP/1.0 Persistent Connections">Appendix&nbsp;C.2</a>.
    17741773      </p>
    17751774      <div id="rfc.iref.c.7"></div>
     
    18441843         requested by the proxy. All Internet-based HTTP/1.1 servers <em class="bcp14">MUST</em> respond with a 400 (Bad Request) status code to any HTTP/1.1 request message which lacks a Host header field.
    18451844      </p>
    1846       <p id="rfc.section.8.4.p.6">See Sections <a href="#the.resource.identified.by.a.request" title="The Resource Identified by a Request">5.2</a> and <a href="#changes.to.simplify.multi-homed.web.servers.and.conserve.ip.addresses" title="Changes to Simplify Multi-homed Web Servers and Conserve IP Addresses">D.1.1</a> for other requirements relating to Host.
     1845      <p id="rfc.section.8.4.p.6">See Sections <a href="#the.resource.identified.by.a.request" title="The Resource Identified by a Request">5.2</a> and <a href="#changes.to.simplify.multi-homed.web.servers.and.conserve.ip.addresses" title="Changes to Simplify Multi-homed Web Servers and Conserve IP Addresses">C.1.1</a> for other requirements relating to Host.
    18471846      </p>
    18481847      <div id="rfc.iref.t.2"></div>
     
    20782077      </div>
    20792078      <p id="rfc.section.9.1.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
     2079      <h2 id="rfc.section.9.2"><a href="#rfc.section.9.2">9.2</a>&nbsp;<a id="internet.media.type.http" href="#internet.media.type.http">Internet Media Type Registrations</a></h2>
     2080      <p id="rfc.section.9.2.p.1">This document serves as the specification for the Internet media types "message/http" and "application/http". The following
     2081         is to be registered with IANA (see <a href="#RFC4288" id="rfc.xref.RFC4288.1"><cite title="Media Type Specifications and Registration Procedures">[RFC4288]</cite></a>).
     2082      </p>
     2083      <div id="rfc.iref.m.2"></div>
     2084      <div id="rfc.iref.m.3"></div>
     2085      <h3 id="rfc.section.9.2.1"><a href="#rfc.section.9.2.1">9.2.1</a>&nbsp;<a id="internet.media.type.message.http" href="#internet.media.type.message.http">Internet Media Type message/http</a></h3>
     2086      <p id="rfc.section.9.2.1.p.1">The message/http type can be used to enclose a single HTTP request or response message, provided that it obeys the MIME restrictions
     2087         for all "message" types regarding line length and encodings.
     2088      </p>
     2089      <p id="rfc.section.9.2.1.p.2"> </p>
     2090      <dl>
     2091         <dt>Type name:</dt>
     2092         <dd>message</dd>
     2093         <dt>Subtype name:</dt>
     2094         <dd>http</dd>
     2095         <dt>Required parameters:</dt>
     2096         <dd>none</dd>
     2097         <dt>Optional parameters:</dt>
     2098         <dd>version, msgtype
     2099            <dl>
     2100               <dt>version:</dt>
     2101               <dd>The HTTP-Version number of the enclosed message (e.g., "1.1"). If not present, the version can be determined from the first
     2102                  line of the body.
     2103               </dd>
     2104               <dt>msgtype:</dt>
     2105               <dd>The message type -- "request" or "response". If not present, the type can be determined from the first line of the body.</dd>
     2106            </dl>
     2107         </dd>
     2108         <dt>Encoding considerations:</dt>
     2109         <dd>only "7bit", "8bit", or "binary" are permitted</dd>
     2110         <dt>Security considerations:</dt>
     2111         <dd>none</dd>
     2112         <dt>Interoperability considerations:</dt>
     2113         <dd>none</dd>
     2114         <dt>Published specification:</dt>
     2115         <dd>This specification (see <a href="#internet.media.type.message.http" title="Internet Media Type message/http">Section&nbsp;9.2.1</a>).
     2116         </dd>
     2117         <dt>Applications that use this media type:</dt>
     2118         <dt>Additional information:</dt>
     2119         <dd>
     2120            <dl>
     2121               <dt>Magic number(s):</dt>
     2122               <dd>none</dd>
     2123               <dt>File extension(s):</dt>
     2124               <dd>none</dd>
     2125               <dt>Macintosh file type code(s):</dt>
     2126               <dd>none</dd>
     2127            </dl>
     2128         </dd>
     2129         <dt>Person and email address to contact for further information:</dt>
     2130         <dd>See Authors Section.</dd>
     2131         <dt>Intended usage:</dt>
     2132         <dd>COMMON</dd>
     2133         <dt>Restrictions on usage:</dt>
     2134         <dd>none</dd>
     2135         <dt>Author/Change controller:</dt>
     2136         <dd>IESG</dd>
     2137      </dl>
     2138      <div id="rfc.iref.m.4"></div>
     2139      <div id="rfc.iref.a.1"></div>
     2140      <h3 id="rfc.section.9.2.2"><a href="#rfc.section.9.2.2">9.2.2</a>&nbsp;<a id="internet.media.type.application.http" href="#internet.media.type.application.http">Internet Media Type application/http</a></h3>
     2141      <p id="rfc.section.9.2.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>
     2142      <p id="rfc.section.9.2.2.p.2"> </p>
     2143      <dl>
     2144         <dt>Type name:</dt>
     2145         <dd>application</dd>
     2146         <dt>Subtype name:</dt>
     2147         <dd>http</dd>
     2148         <dt>Required parameters:</dt>
     2149         <dd>none</dd>
     2150         <dt>Optional parameters:</dt>
     2151         <dd>version, msgtype
     2152            <dl>
     2153               <dt>version:</dt>
     2154               <dd>The HTTP-Version number of the enclosed messages (e.g., "1.1"). If not present, the version can be determined from the first
     2155                  line of the body.
     2156               </dd>
     2157               <dt>msgtype:</dt>
     2158               <dd>The message type -- "request" or "response". If not present, the type can be determined from the first line of the body.</dd>
     2159            </dl>
     2160         </dd>
     2161         <dt>Encoding considerations:</dt>
     2162         <dd>HTTP messages enclosed by this type are in "binary" format; use of an appropriate Content-Transfer-Encoding is required when
     2163            transmitted via E-mail.
     2164         </dd>
     2165         <dt>Security considerations:</dt>
     2166         <dd>none</dd>
     2167         <dt>Interoperability considerations:</dt>
     2168         <dd>none</dd>
     2169         <dt>Published specification:</dt>
     2170         <dd>This specification (see <a href="#internet.media.type.application.http" title="Internet Media Type application/http">Section&nbsp;9.2.2</a>).
     2171         </dd>
     2172         <dt>Applications that use this media type:</dt>
     2173         <dt>Additional information:</dt>
     2174         <dd>
     2175            <dl>
     2176               <dt>Magic number(s):</dt>
     2177               <dd>none</dd>
     2178               <dt>File extension(s):</dt>
     2179               <dd>none</dd>
     2180               <dt>Macintosh file type code(s):</dt>
     2181               <dd>none</dd>
     2182            </dl>
     2183         </dd>
     2184         <dt>Person and email address to contact for further information:</dt>
     2185         <dd>See Authors Section.</dd>
     2186         <dt>Intended usage:</dt>
     2187         <dd>COMMON</dd>
     2188         <dt>Restrictions on usage:</dt>
     2189         <dd>none</dd>
     2190         <dt>Author/Change controller:</dt>
     2191         <dd>IESG</dd>
     2192      </dl>
    20802193      <h1 id="rfc.section.10"><a href="#rfc.section.10">10.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
    20812194      <p id="rfc.section.10.p.1">This section is meant to inform application developers, information providers, and users of the security limitations in HTTP/1.1
     
    23822495            (editor)
    23832496            <span class="n hidden"><span class="family-name">Reschke</span><span class="given-name">Julian F.</span></span></span><span class="org vcardline">greenbytes GmbH</span><span class="adr"><span class="street-address vcardline">Hafenweg 16</span><span class="vcardline"><span class="locality">Muenster</span>, <span class="region">NW</span>&nbsp;<span class="postal-code">48155</span></span><span class="country-name vcardline">Germany</span></span><span class="vcardline tel">Phone: <a href="tel:+492512807760"><span class="value">+49 251 2807760</span></a></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+492512807761"><span class="value">+49 251 2807761</span></a></span><span class="vcardline">EMail: <a><span class="email">julian.reschke@greenbytes.de</span></a></span><span class="vcardline">URI: <a href="http://greenbytes.de/tech/webdav/" class="url">http://greenbytes.de/tech/webdav/</a></span></address>
    2384       <h1 id="rfc.section.A"><a href="#rfc.section.A">A.</a>&nbsp;<a id="internet.media.type.http" href="#internet.media.type.http">Internet Media Types</a></h1>
    2385       <p id="rfc.section.A.p.1">In addition to defining HTTP/1.1, this document serves as the specification for the Internet media type "message/http" and
    2386          "application/http". The following is to be registered with IANA <a href="#RFC4288" id="rfc.xref.RFC4288.1"><cite title="Media Type Specifications and Registration Procedures">[RFC4288]</cite></a>.
    2387       </p>
    2388       <div id="rfc.iref.m.2"></div>
    2389       <div id="rfc.iref.m.3"></div>
    2390       <h2 id="rfc.section.A.1"><a href="#rfc.section.A.1">A.1</a>&nbsp;<a id="internet.media.type.message.http" href="#internet.media.type.message.http">Internet Media Type message/http</a></h2>
    2391       <p id="rfc.section.A.1.p.1">The message/http type can be used to enclose a single HTTP request or response message, provided that it obeys the MIME restrictions
    2392          for all "message" types regarding line length and encodings.
    2393       </p>
    2394       <p id="rfc.section.A.1.p.2"> </p>
    2395       <dl>
    2396          <dt>Type name:</dt>
    2397          <dd>message</dd>
    2398          <dt>Subtype name:</dt>
    2399          <dd>http</dd>
    2400          <dt>Required parameters:</dt>
    2401          <dd>none</dd>
    2402          <dt>Optional parameters:</dt>
    2403          <dd>version, msgtype
    2404             <dl>
    2405                <dt>version:</dt>
    2406                <dd>The HTTP-Version number of the enclosed message (e.g., "1.1"). If not present, the version can be determined from the first
    2407                   line of the body.
    2408                </dd>
    2409                <dt>msgtype:</dt>
    2410                <dd>The message type -- "request" or "response". If not present, the type can be determined from the first line of the body.</dd>
    2411             </dl>
    2412          </dd>
    2413          <dt>Encoding considerations:</dt>
    2414          <dd>only "7bit", "8bit", or "binary" are permitted</dd>
    2415          <dt>Security considerations:</dt>
    2416          <dd>none</dd>
    2417          <dt>Interoperability considerations:</dt>
    2418          <dd>none</dd>
    2419          <dt>Published specification:</dt>
    2420          <dd>This specification (see <a href="#internet.media.type.message.http" title="Internet Media Type message/http">Appendix&nbsp;A.1</a>).
    2421          </dd>
    2422          <dt>Applications that use this media type:</dt>
    2423          <dt>Additional information:</dt>
    2424          <dd>
    2425             <dl>
    2426                <dt>Magic number(s):</dt>
    2427                <dd>none</dd>
    2428                <dt>File extension(s):</dt>
    2429                <dd>none</dd>
    2430                <dt>Macintosh file type code(s):</dt>
    2431                <dd>none</dd>
    2432             </dl>
    2433          </dd>
    2434          <dt>Person and email address to contact for further information:</dt>
    2435          <dd>See Authors Section.</dd>
    2436          <dt>Intended usage:</dt>
    2437          <dd>COMMON</dd>
    2438          <dt>Restrictions on usage:</dt>
    2439          <dd>none</dd>
    2440          <dt>Author/Change controller:</dt>
    2441          <dd>IESG</dd>
    2442       </dl>
    2443       <div id="rfc.iref.m.4"></div>
    2444       <div id="rfc.iref.a.1"></div>
    2445       <h2 id="rfc.section.A.2"><a href="#rfc.section.A.2">A.2</a>&nbsp;<a id="internet.media.type.application.http" href="#internet.media.type.application.http">Internet Media Type application/http</a></h2>
    2446       <p id="rfc.section.A.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>
    2447       <p id="rfc.section.A.2.p.2"> </p>
    2448       <dl>
    2449          <dt>Type name:</dt>
    2450          <dd>application</dd>
    2451          <dt>Subtype name:</dt>
    2452          <dd>http</dd>
    2453          <dt>Required parameters:</dt>
    2454          <dd>none</dd>
    2455          <dt>Optional parameters:</dt>
    2456          <dd>version, msgtype
    2457             <dl>
    2458                <dt>version:</dt>
    2459                <dd>The HTTP-Version number of the enclosed messages (e.g., "1.1"). If not present, the version can be determined from the first
    2460                   line of the body.
    2461                </dd>
    2462                <dt>msgtype:</dt>
    2463                <dd>The message type -- "request" or "response". If not present, the type can be determined from the first line of the body.</dd>
    2464             </dl>
    2465          </dd>
    2466          <dt>Encoding considerations:</dt>
    2467          <dd>HTTP messages enclosed by this type are in "binary" format; use of an appropriate Content-Transfer-Encoding is required when
    2468             transmitted via E-mail.
    2469          </dd>
    2470          <dt>Security considerations:</dt>
    2471          <dd>none</dd>
    2472          <dt>Interoperability considerations:</dt>
    2473          <dd>none</dd>
    2474          <dt>Published specification:</dt>
    2475          <dd>This specification (see <a href="#internet.media.type.application.http" title="Internet Media Type application/http">Appendix&nbsp;A.2</a>).
    2476          </dd>
    2477          <dt>Applications that use this media type:</dt>
    2478          <dt>Additional information:</dt>
    2479          <dd>
    2480             <dl>
    2481                <dt>Magic number(s):</dt>
    2482                <dd>none</dd>
    2483                <dt>File extension(s):</dt>
    2484                <dd>none</dd>
    2485                <dt>Macintosh file type code(s):</dt>
    2486                <dd>none</dd>
    2487             </dl>
    2488          </dd>
    2489          <dt>Person and email address to contact for further information:</dt>
    2490          <dd>See Authors Section.</dd>
    2491          <dt>Intended usage:</dt>
    2492          <dd>COMMON</dd>
    2493          <dt>Restrictions on usage:</dt>
    2494          <dd>none</dd>
    2495          <dt>Author/Change controller:</dt>
    2496          <dd>IESG</dd>
    2497       </dl>
    2498       <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="tolerant.applications" href="#tolerant.applications">Tolerant Applications</a></h1>
    2499       <p id="rfc.section.B.p.1">Although this document specifies the requirements for the generation of HTTP/1.1 messages, not all applications will be correct
     2497      <h1 id="rfc.section.A"><a href="#rfc.section.A">A.</a>&nbsp;<a id="tolerant.applications" href="#tolerant.applications">Tolerant Applications</a></h1>
     2498      <p id="rfc.section.A.p.1">Although this document specifies the requirements for the generation of HTTP/1.1 messages, not all applications will be correct
    25002499         in their implementation. We therefore recommend that operational applications be tolerant of deviations whenever those deviations
    25012500         can be interpreted unambiguously.
    25022501      </p>
    2503       <p id="rfc.section.B.p.2">Clients <em class="bcp14">SHOULD</em> be tolerant in parsing the Status-Line and servers tolerant when parsing the Request-Line. In particular, they <em class="bcp14">SHOULD</em> accept any amount of SP or HTAB characters between fields, even though only a single SP is required.
    2504       </p>
    2505       <p id="rfc.section.B.p.3">The line terminator for message-header fields is the sequence CRLF. However, we recommend that applications, when parsing
     2502      <p id="rfc.section.A.p.2">Clients <em class="bcp14">SHOULD</em> be tolerant in parsing the Status-Line and servers tolerant when parsing the Request-Line. In particular, they <em class="bcp14">SHOULD</em> accept any amount of SP or HTAB characters between fields, even though only a single SP is required.
     2503      </p>
     2504      <p id="rfc.section.A.p.3">The line terminator for message-header fields is the sequence CRLF. However, we recommend that applications, when parsing
    25062505         such headers, recognize a single LF as a line terminator and ignore the leading CR.
    25072506      </p>
    2508       <p id="rfc.section.B.p.4">The character set of an entity-body <em class="bcp14">SHOULD</em> be labeled as the lowest common denominator of the character codes used within that body, with the exception that not labeling
     2507      <p id="rfc.section.A.p.4">The character set of an entity-body <em class="bcp14">SHOULD</em> be labeled as the lowest common denominator of the character codes used within that body, with the exception that not labeling
    25092508         the entity is preferred over labeling the entity with the labels US-ASCII or ISO-8859-1. See <a href="#Part3" id="rfc.xref.Part3.15"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>.
    25102509      </p>
    2511       <p id="rfc.section.B.p.5">Additional rules for requirements on parsing and encoding of dates and other potential problems with date encodings include:</p>
    2512       <p id="rfc.section.B.p.6"> </p>
     2510      <p id="rfc.section.A.p.5">Additional rules for requirements on parsing and encoding of dates and other potential problems with date encodings include:</p>
     2511      <p id="rfc.section.A.p.6"> </p>
    25132512      <ul>
    25142513         <li>HTTP/1.1 clients and caches <em class="bcp14">SHOULD</em> assume that an RFC-850 date which appears to be more than 50 years in the future is in fact in the past (this helps solve
     
    25222521         </li>
    25232522      </ul>
    2524       <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="conversion.of.date.formats" href="#conversion.of.date.formats">Conversion of Date Formats</a></h1>
    2525       <p id="rfc.section.C.p.1">HTTP/1.1 uses a restricted set of date formats (<a href="#full.date" title="Full Date">Section&nbsp;3.3.1</a>) to simplify the process of date comparison. Proxies and gateways from other protocols <em class="bcp14">SHOULD</em> ensure that any Date header field present in a message conforms to one of the HTTP/1.1 formats and rewrite the date if necessary.
    2526       </p>
    2527       <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1>
    2528       <p id="rfc.section.D.p.1">It is beyond the scope of a protocol specification to mandate compliance with previous versions. HTTP/1.1 was deliberately
     2523      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="conversion.of.date.formats" href="#conversion.of.date.formats">Conversion of Date Formats</a></h1>
     2524      <p id="rfc.section.B.p.1">HTTP/1.1 uses a restricted set of date formats (<a href="#full.date" title="Full Date">Section&nbsp;3.3.1</a>) to simplify the process of date comparison. Proxies and gateways from other protocols <em class="bcp14">SHOULD</em> ensure that any Date header field present in a message conforms to one of the HTTP/1.1 formats and rewrite the date if necessary.
     2525      </p>
     2526      <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1>
     2527      <p id="rfc.section.C.p.1">It is beyond the scope of a protocol specification to mandate compliance with previous versions. HTTP/1.1 was deliberately
    25292528         designed, however, to make supporting previous versions easy. It is worth noting that, at the time of composing this specification
    25302529         (1996), we would expect commercial HTTP/1.1 servers to:
     
    25352534         <li>respond appropriately with a message in the same major version used by the client.</li>
    25362535      </ul>
    2537       <p id="rfc.section.D.p.2">And we would expect HTTP/1.1 clients to: </p>
     2536      <p id="rfc.section.C.p.2">And we would expect HTTP/1.1 clients to: </p>
    25382537      <ul>
    25392538         <li>recognize the format of the Status-Line for HTTP/1.0 and 1.1 responses;</li>
    25402539         <li>understand any valid response in the format of HTTP/0.9, 1.0, or 1.1.</li>
    25412540      </ul>
    2542       <p id="rfc.section.D.p.3">For most implementations of HTTP/1.0, each connection is established by the client prior to the request and closed by the
     2541      <p id="rfc.section.C.p.3">For most implementations of HTTP/1.0, each connection is established by the client prior to the request and closed by the
    25432542         server after sending the response. Some implementations implement the Keep-Alive version of persistent connections described
    25442543         in <a href="http://tools.ietf.org/html/rfc2068#section-19.7.1">Section 19.7.1</a> of <a href="#RFC2068" id="rfc.xref.RFC2068.6"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>.
    25452544      </p>
    2546       <h2 id="rfc.section.D.1"><a href="#rfc.section.D.1">D.1</a>&nbsp;<a id="changes.from.1.0" href="#changes.from.1.0">Changes from HTTP/1.0</a></h2>
    2547       <p id="rfc.section.D.1.p.1">This section summarizes major differences between versions HTTP/1.0 and HTTP/1.1.</p>
    2548       <h3 id="rfc.section.D.1.1"><a href="#rfc.section.D.1.1">D.1.1</a>&nbsp;<a id="changes.to.simplify.multi-homed.web.servers.and.conserve.ip.addresses" href="#changes.to.simplify.multi-homed.web.servers.and.conserve.ip.addresses">Changes to Simplify Multi-homed Web Servers and Conserve IP Addresses</a></h3>
    2549       <p id="rfc.section.D.1.1.p.1">The requirements that clients and servers support the Host request-header, report an error if the Host request-header (<a href="#header.host" id="rfc.xref.header.host.2" title="Host">Section&nbsp;8.4</a>) is missing from an HTTP/1.1 request, and accept absolute URIs (<a href="#request-uri" title="Request-URI">Section&nbsp;5.1.2</a>) are among the most important changes defined by this specification.
    2550       </p>
    2551       <p id="rfc.section.D.1.1.p.2">Older HTTP/1.0 clients assumed a one-to-one relationship of IP addresses and servers; there was no other established mechanism
     2545      <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a>&nbsp;<a id="changes.from.1.0" href="#changes.from.1.0">Changes from HTTP/1.0</a></h2>
     2546      <p id="rfc.section.C.1.p.1">This section summarizes major differences between versions HTTP/1.0 and HTTP/1.1.</p>
     2547      <h3 id="rfc.section.C.1.1"><a href="#rfc.section.C.1.1">C.1.1</a>&nbsp;<a id="changes.to.simplify.multi-homed.web.servers.and.conserve.ip.addresses" href="#changes.to.simplify.multi-homed.web.servers.and.conserve.ip.addresses">Changes to Simplify Multi-homed Web Servers and Conserve IP Addresses</a></h3>
     2548      <p id="rfc.section.C.1.1.p.1">The requirements that clients and servers support the Host request-header, report an error if the Host request-header (<a href="#header.host" id="rfc.xref.header.host.2" title="Host">Section&nbsp;8.4</a>) is missing from an HTTP/1.1 request, and accept absolute URIs (<a href="#request-uri" title="Request-URI">Section&nbsp;5.1.2</a>) are among the most important changes defined by this specification.
     2549      </p>
     2550      <p id="rfc.section.C.1.1.p.2">Older HTTP/1.0 clients assumed a one-to-one relationship of IP addresses and servers; there was no other established mechanism
    25522551         for distinguishing the intended server of a request than the IP address to which that request was directed. The changes outlined
    25532552         above will allow the Internet, once older HTTP clients are no longer common, to support multiple Web sites from a single IP
     
    25682567         </li>
    25692568      </ul>
    2570       <h2 id="rfc.section.D.2"><a href="#rfc.section.D.2">D.2</a>&nbsp;<a id="compatibility.with.http.1.0.persistent.connections" href="#compatibility.with.http.1.0.persistent.connections">Compatibility with HTTP/1.0 Persistent Connections</a></h2>
    2571       <p id="rfc.section.D.2.p.1">Some clients and servers might wish to be compatible with some previous implementations of persistent connections in HTTP/1.0
     2569      <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a>&nbsp;<a id="compatibility.with.http.1.0.persistent.connections" href="#compatibility.with.http.1.0.persistent.connections">Compatibility with HTTP/1.0 Persistent Connections</a></h2>
     2570      <p id="rfc.section.C.2.p.1">Some clients and servers might wish to be compatible with some previous implementations of persistent connections in HTTP/1.0
    25722571         clients and servers. Persistent connections in HTTP/1.0 are explicitly negotiated as they are not the default behavior. HTTP/1.0
    25732572         experimental implementations of persistent connections are faulty, and the new facilities in HTTP/1.1 are designed to rectify
     
    25772576         from using Keep-Alive when talking to proxies.
    25782577      </p>
    2579       <p id="rfc.section.D.2.p.2">However, talking to proxies is the most important use of persistent connections, so that prohibition is clearly unacceptable.
     2578      <p id="rfc.section.C.2.p.2">However, talking to proxies is the most important use of persistent connections, so that prohibition is clearly unacceptable.
    25802579         Therefore, we need some other mechanism for indicating a persistent connection is desired, which is safe to use even when
    25812580         talking to an old proxy that ignores Connection. Persistent connections are the default for HTTP/1.1 messages; we introduce
    25822581         a new keyword (Connection: close) for declaring non-persistence. See <a href="#header.connection" id="rfc.xref.header.connection.7" title="Connection">Section&nbsp;8.1</a>.
    25832582      </p>
    2584       <p id="rfc.section.D.2.p.3">The original HTTP/1.0 form of persistent connections (the Connection: Keep-Alive and Keep-Alive header) is documented in <a href="#RFC2068" id="rfc.xref.RFC2068.7"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>.
    2585       </p>
    2586       <h2 id="rfc.section.D.3"><a href="#rfc.section.D.3">D.3</a>&nbsp;<a id="changes.from.rfc.2068" href="#changes.from.rfc.2068">Changes from RFC 2068</a></h2>
    2587       <p id="rfc.section.D.3.p.1">This specification has been carefully audited to correct and disambiguate key word usage; RFC 2068 had many problems in respect
     2583      <p id="rfc.section.C.2.p.3">The original HTTP/1.0 form of persistent connections (the Connection: Keep-Alive and Keep-Alive header) is documented in <a href="#RFC2068" id="rfc.xref.RFC2068.7"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>.
     2584      </p>
     2585      <h2 id="rfc.section.C.3"><a href="#rfc.section.C.3">C.3</a>&nbsp;<a id="changes.from.rfc.2068" href="#changes.from.rfc.2068">Changes from RFC 2068</a></h2>
     2586      <p id="rfc.section.C.3.p.1">This specification has been carefully audited to correct and disambiguate key word usage; RFC 2068 had many problems in respect
    25882587         to the conventions laid out in <a href="#RFC2119" id="rfc.xref.RFC2119.2"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a>.
    25892588      </p>
    2590       <p id="rfc.section.D.3.p.2">Transfer-coding and message lengths all interact in ways that required fixing exactly when chunked encoding is used (to allow
     2589      <p id="rfc.section.C.3.p.2">Transfer-coding and message lengths all interact in ways that required fixing exactly when chunked encoding is used (to allow
    25912590         for transfer encoding that may not be self delimiting); it was important to straighten out exactly how message lengths are
    25922591         computed. (Sections <a href="#transfer.codings" title="Transfer Codings">3.4</a>, <a href="#message.length" title="Message Length">4.4</a>, <a href="#header.content-length" id="rfc.xref.header.content-length.3" title="Content-Length">8.2</a>, see also <a href="#Part3" id="rfc.xref.Part3.16"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="#Part5" id="rfc.xref.Part5.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a> and <a href="#Part6" id="rfc.xref.Part6.9"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>)
    25932592      </p>
    2594       <p id="rfc.section.D.3.p.3">The use and interpretation of HTTP version numbers has been clarified by <a href="#RFC2145" id="rfc.xref.RFC2145.3"><cite title="Use and Interpretation of HTTP Version Numbers">[RFC2145]</cite></a>. Require proxies to upgrade requests to highest protocol version they support to deal with problems discovered in HTTP/1.0
     2593      <p id="rfc.section.C.3.p.3">The use and interpretation of HTTP version numbers has been clarified by <a href="#RFC2145" id="rfc.xref.RFC2145.3"><cite title="Use and Interpretation of HTTP Version Numbers">[RFC2145]</cite></a>. Require proxies to upgrade requests to highest protocol version they support to deal with problems discovered in HTTP/1.0
    25952594         implementations (<a href="#http.version" title="HTTP Version">Section&nbsp;3.1</a>)
    25962595      </p>
    2597       <p id="rfc.section.D.3.p.4">Transfer-coding had significant problems, particularly with interactions with chunked encoding. The solution is that transfer-codings
     2596      <p id="rfc.section.C.3.p.4">Transfer-coding had significant problems, particularly with interactions with chunked encoding. The solution is that transfer-codings
    25982597         become as full fledged as content-codings. This involves adding an IANA registry for transfer-codings (separate from content
    25992598         codings), a new header field (TE) and enabling trailer headers in the future. Transfer encoding is a major performance benefit,
     
    26012600         authentication trailers, chunked encoding and HTTP/1.0 clients.(Section <a href="#transfer.codings" title="Transfer Codings">3.4</a>, <a href="#chunked.transfer.encoding" title="Chunked Transfer Coding">3.4.1</a>, and <a href="#header.te" id="rfc.xref.header.te.4" title="TE">8.5</a>)
    26022601      </p>
    2603       <h2 id="rfc.section.D.4"><a href="#rfc.section.D.4">D.4</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
    2604       <p id="rfc.section.D.4.p.1">The CHAR rule does not allow the NUL character anymore (this affects the comment and quoted-string rules). Furthermore, the
     2602      <h2 id="rfc.section.C.4"><a href="#rfc.section.C.4">C.4</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
     2603      <p id="rfc.section.C.4.p.1">The CHAR rule does not allow the NUL character anymore (this affects the comment and quoted-string rules). Furthermore, the
    26052604         quoted-pair rule does not allow escaping NUL, CR or LF anymore. (<a href="#basic.rules" title="Basic Rules">Section&nbsp;2.2</a>)
    26062605      </p>
    2607       <p id="rfc.section.D.4.p.2">Clarify that HTTP-Version is case sensitive. (<a href="#http.version" title="HTTP Version">Section&nbsp;3.1</a>)
    2608       </p>
    2609       <p id="rfc.section.D.4.p.3">Remove reference to non-existant identity transfer-coding value tokens. (Sections <a href="#transfer.codings" title="Transfer Codings">3.4</a> and <a href="#message.length" title="Message Length">4.4</a>)
    2610       </p>
    2611       <p id="rfc.section.D.4.p.4">Clarification that the chunk length does not include the count of the octets in the chunk header and trailer. (<a href="#chunked.transfer.encoding" title="Chunked Transfer Coding">Section&nbsp;3.4.1</a>)
    2612       </p>
    2613       <p id="rfc.section.D.4.p.5">Fix BNF to add query, as the abs_path production in <a href="http://tools.ietf.org/html/rfc2396#section-3">Section 3</a> of <a href="#RFC2396" id="rfc.xref.RFC2396.12"><cite title="Uniform Resource Identifiers (URI): Generic Syntax">[RFC2396]</cite></a> doesn't define it. (<a href="#request-uri" title="Request-URI">Section&nbsp;5.1.2</a>)
    2614       </p>
    2615       <p id="rfc.section.D.4.p.6">Clarify exactly when close connection options must be sent. (<a href="#header.connection" id="rfc.xref.header.connection.8" title="Connection">Section&nbsp;8.1</a>)
    2616       </p>
    2617       <h1 id="rfc.section.E"><a href="#rfc.section.E">E.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
    2618       <h2 id="rfc.section.E.1"><a href="#rfc.section.E.1">E.1</a>&nbsp;Since RFC2616
     2606      <p id="rfc.section.C.4.p.2">Clarify that HTTP-Version is case sensitive. (<a href="#http.version" title="HTTP Version">Section&nbsp;3.1</a>)
     2607      </p>
     2608      <p id="rfc.section.C.4.p.3">Remove reference to non-existant identity transfer-coding value tokens. (Sections <a href="#transfer.codings" title="Transfer Codings">3.4</a> and <a href="#message.length" title="Message Length">4.4</a>)
     2609      </p>
     2610      <p id="rfc.section.C.4.p.4">Clarification that the chunk length does not include the count of the octets in the chunk header and trailer. (<a href="#chunked.transfer.encoding" title="Chunked Transfer Coding">Section&nbsp;3.4.1</a>)
     2611      </p>
     2612      <p id="rfc.section.C.4.p.5">Fix BNF to add query, as the abs_path production in <a href="http://tools.ietf.org/html/rfc2396#section-3">Section 3</a> of <a href="#RFC2396" id="rfc.xref.RFC2396.12"><cite title="Uniform Resource Identifiers (URI): Generic Syntax">[RFC2396]</cite></a> doesn't define it. (<a href="#request-uri" title="Request-URI">Section&nbsp;5.1.2</a>)
     2613      </p>
     2614      <p id="rfc.section.C.4.p.6">Clarify exactly when close connection options must be sent. (<a href="#header.connection" id="rfc.xref.header.connection.8" title="Connection">Section&nbsp;8.1</a>)
     2615      </p>
     2616      <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>
     2617      <h2 id="rfc.section.D.1"><a href="#rfc.section.D.1">D.1</a>&nbsp;Since RFC2616
    26192618      </h2>
    2620       <p id="rfc.section.E.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.4"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
    2621       </p>
    2622       <h2 id="rfc.section.E.2"><a href="#rfc.section.E.2">E.2</a>&nbsp;Since draft-ietf-httpbis-p1-messaging-00
     2619      <p id="rfc.section.D.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.4"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
     2620      </p>
     2621      <h2 id="rfc.section.D.2"><a href="#rfc.section.D.2">D.2</a>&nbsp;Since draft-ietf-httpbis-p1-messaging-00
    26232622      </h2>
    2624       <p id="rfc.section.E.2.p.1">Closed issues: </p>
     2623      <p id="rfc.section.D.2.p.1">Closed issues: </p>
    26252624      <ul>
    26262625         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/1">http://www3.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;)
     
    26632662         </li>
    26642663      </ul>
    2665       <p id="rfc.section.E.2.p.2">Other changes: </p>
     2664      <p id="rfc.section.D.2.p.2">Other changes: </p>
    26662665      <ul>
    26672666         <li>Update media type registrations to use RFC4288 template.</li>
     
    26692668         </li>
    26702669      </ul>
    2671       <h2 id="rfc.section.E.3"><a href="#rfc.section.E.3">E.3</a>&nbsp;Since draft-ietf-httpbis-p1-messaging-01
     2670      <h2 id="rfc.section.D.3"><a href="#rfc.section.D.3">D.3</a>&nbsp;Since draft-ietf-httpbis-p1-messaging-01
    26722671      </h2>
    2673       <p id="rfc.section.E.3.p.1">Closed issues: </p>
     2672      <p id="rfc.section.D.3.p.1">Closed issues: </p>
    26742673      <ul>
    26752674         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/19">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/19</a>&gt;: "Bodies on GET (and other) requests"
     
    26822681         </li>
    26832682      </ul>
    2684       <p id="rfc.section.E.3.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
     2683      <p id="rfc.section.D.3.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
    26852684      </p>
    26862685      <ul>
     
    26972696         <li>Rewrite prose rule "token" in terms of "tchar", rewrite prose rule "TEXT".</li>
    26982697      </ul>
    2699       <h2 id="rfc.section.E.4"><a href="#rfc.section.E.4">E.4</a>&nbsp;<a id="changes.since.02" href="#changes.since.02">Since draft-ietf-httpbis-p1-messaging-02</a></h2>
    2700       <p id="rfc.section.E.4.p.1">Closed issues: </p>
     2698      <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>
     2699      <p id="rfc.section.D.4.p.1">Closed issues: </p>
    27012700      <ul>
    27022701         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/51">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/51</a>&gt;: "HTTP-date vs. rfc1123-date"
     
    27052704         </li>
    27062705      </ul>
    2707       <p id="rfc.section.E.4.p.2">Ongoing work on IANA Message Header Registration (&lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/40">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/40</a>&gt;):
     2706      <p id="rfc.section.D.4.p.2">Ongoing work on IANA Message Header Registration (&lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/40">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/40</a>&gt;):
    27082707      </p>
    27092708      <ul>
    27102709         <li>Reference RFC 3984, and update header registrations for headers defined in this document.</li>
    27112710      </ul>
    2712       <p id="rfc.section.E.4.p.3">Ongoing work on ABNF conversion (&lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
     2711      <p id="rfc.section.D.4.p.3">Ongoing work on ABNF conversion (&lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
    27132712      </p>
    27142713      <ul>
    27152714         <li>Replace string literals when the string really is case-sensitive (HTTP-Version).</li>
    27162715      </ul>
    2717       <h2 id="rfc.section.E.5"><a href="#rfc.section.E.5">E.5</a>&nbsp;<a id="changes.since.03" href="#changes.since.03">Since draft-ietf-httpbis-p1-messaging-03</a></h2>
    2718       <p id="rfc.section.E.5.p.1">Closed issues: </p>
     2716      <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>
     2717      <p id="rfc.section.D.5.p.1">Closed issues: </p>
    27192718      <ul>
    27202719         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/28">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/28</a>&gt;: "Connection closing"
    27212720         </li>
     2721         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/97">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/97</a>&gt;: "Move registrations and registry information to IANA Considerations"
     2722         </li>
    27222723         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/120">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/120</a>&gt;: "need new URL for PAD1995 reference"
    27232724         </li>
    27242725      </ul>
    2725       <p id="rfc.section.E.5.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
     2726      <p id="rfc.section.D.5.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
    27262727      </p>
    27272728      <ul>
     
    27582759         <ul class="ind">
    27592760            <li class="indline0"><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul class="ind">
    2760                   <li class="indline1">application/http Media Type&nbsp;&nbsp;<a class="iref" href="#rfc.iref.a.1"><b>A.2</b></a></li>
     2761                  <li class="indline1">application/http Media Type&nbsp;&nbsp;<a class="iref" href="#rfc.iref.a.1"><b>9.2.2</b></a></li>
    27612762               </ul>
    27622763            </li>
     
    27662767                  <li class="indline1">client&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.3">1.3</a></li>
    27672768                  <li class="indline1">connection&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.1">1.3</a></li>
    2768                   <li class="indline1">Connection header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.connection.1">4.5</a>, <a class="iref" href="#rfc.xref.header.connection.2">7.1.2</a>, <a class="iref" href="#rfc.xref.header.connection.3">7.1.3</a>, <a class="iref" href="#rfc.iref.c.6"><b>8.1</b></a>, <a class="iref" href="#rfc.xref.header.connection.4">8.5</a>, <a class="iref" href="#rfc.xref.header.connection.5">8.8</a>, <a class="iref" href="#rfc.xref.header.connection.6">9.1</a>, <a class="iref" href="#rfc.xref.header.connection.7">D.2</a>, <a class="iref" href="#rfc.xref.header.connection.8">D.4</a></li>
     2769                  <li class="indline1">Connection header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.connection.1">4.5</a>, <a class="iref" href="#rfc.xref.header.connection.2">7.1.2</a>, <a class="iref" href="#rfc.xref.header.connection.3">7.1.3</a>, <a class="iref" href="#rfc.iref.c.6"><b>8.1</b></a>, <a class="iref" href="#rfc.xref.header.connection.4">8.5</a>, <a class="iref" href="#rfc.xref.header.connection.5">8.8</a>, <a class="iref" href="#rfc.xref.header.connection.6">9.1</a>, <a class="iref" href="#rfc.xref.header.connection.7">C.2</a>, <a class="iref" href="#rfc.xref.header.connection.8">C.4</a></li>
    27692770                  <li class="indline1">content negotiation&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.2">1.3</a></li>
    2770                   <li class="indline1">Content-Length header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-length.1">4.4</a>, <a class="iref" href="#rfc.iref.c.7"><b>8.2</b></a>, <a class="iref" href="#rfc.xref.header.content-length.2">9.1</a>, <a class="iref" href="#rfc.xref.header.content-length.3">D.3</a></li>
     2771                  <li class="indline1">Content-Length header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-length.1">4.4</a>, <a class="iref" href="#rfc.iref.c.7"><b>8.2</b></a>, <a class="iref" href="#rfc.xref.header.content-length.2">9.1</a>, <a class="iref" href="#rfc.xref.header.content-length.3">C.3</a></li>
    27712772               </ul>
    27722773            </li>
     
    28872888                  <li class="indline1">Headers&nbsp;&nbsp;
    28882889                     <ul class="ind">
    2889                         <li class="indline1">Connection&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.connection.1">4.5</a>, <a class="iref" href="#rfc.xref.header.connection.2">7.1.2</a>, <a class="iref" href="#rfc.xref.header.connection.3">7.1.3</a>, <a class="iref" href="#rfc.iref.h.1"><b>8.1</b></a>, <a class="iref" href="#rfc.xref.header.connection.4">8.5</a>, <a class="iref" href="#rfc.xref.header.connection.5">8.8</a>, <a class="iref" href="#rfc.xref.header.connection.6">9.1</a>, <a class="iref" href="#rfc.xref.header.connection.7">D.2</a>, <a class="iref" href="#rfc.xref.header.connection.8">D.4</a></li>
    2890                         <li class="indline1">Content-Length&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-length.1">4.4</a>, <a class="iref" href="#rfc.iref.h.2"><b>8.2</b></a>, <a class="iref" href="#rfc.xref.header.content-length.2">9.1</a>, <a class="iref" href="#rfc.xref.header.content-length.3">D.3</a></li>
     2890                        <li class="indline1">Connection&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.connection.1">4.5</a>, <a class="iref" href="#rfc.xref.header.connection.2">7.1.2</a>, <a class="iref" href="#rfc.xref.header.connection.3">7.1.3</a>, <a class="iref" href="#rfc.iref.h.1"><b>8.1</b></a>, <a class="iref" href="#rfc.xref.header.connection.4">8.5</a>, <a class="iref" href="#rfc.xref.header.connection.5">8.8</a>, <a class="iref" href="#rfc.xref.header.connection.6">9.1</a>, <a class="iref" href="#rfc.xref.header.connection.7">C.2</a>, <a class="iref" href="#rfc.xref.header.connection.8">C.4</a></li>
     2891                        <li class="indline1">Content-Length&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-length.1">4.4</a>, <a class="iref" href="#rfc.iref.h.2"><b>8.2</b></a>, <a class="iref" href="#rfc.xref.header.content-length.2">9.1</a>, <a class="iref" href="#rfc.xref.header.content-length.3">C.3</a></li>
    28912892                        <li class="indline1">Date&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.date.1">4.5</a>, <a class="iref" href="#rfc.iref.h.3"><b>8.3</b></a>, <a class="iref" href="#rfc.xref.header.date.2">9.1</a></li>
    2892                         <li class="indline1">Host&nbsp;&nbsp;<a class="iref" href="#rfc.iref.h.5"><b>8.4</b></a>, <a class="iref" href="#rfc.xref.header.host.1">9.1</a>, <a class="iref" href="#rfc.xref.header.host.2">D.1.1</a></li>
    2893                         <li class="indline1">TE&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.te.1">3.4</a>, <a class="iref" href="#rfc.xref.header.te.2">3.4.1</a>, <a class="iref" href="#rfc.iref.h.6"><b>8.5</b></a>, <a class="iref" href="#rfc.xref.header.te.3">9.1</a>, <a class="iref" href="#rfc.xref.header.te.4">D.3</a></li>
     2893                        <li class="indline1">Host&nbsp;&nbsp;<a class="iref" href="#rfc.iref.h.5"><b>8.4</b></a>, <a class="iref" href="#rfc.xref.header.host.1">9.1</a>, <a class="iref" href="#rfc.xref.header.host.2">C.1.1</a></li>
     2894                        <li class="indline1">TE&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.te.1">3.4</a>, <a class="iref" href="#rfc.xref.header.te.2">3.4.1</a>, <a class="iref" href="#rfc.iref.h.6"><b>8.5</b></a>, <a class="iref" href="#rfc.xref.header.te.3">9.1</a>, <a class="iref" href="#rfc.xref.header.te.4">C.3</a></li>
    28942895                        <li class="indline1">Trailer&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.trailer.1">3.4.1</a>, <a class="iref" href="#rfc.xref.header.trailer.2">4.5</a>, <a class="iref" href="#rfc.iref.h.7"><b>8.6</b></a>, <a class="iref" href="#rfc.xref.header.trailer.3">9.1</a></li>
    28952896                        <li class="indline1">Transfer-Encoding&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.transfer-encoding.1">3.4</a>, <a class="iref" href="#rfc.xref.header.transfer-encoding.2">4.3</a>, <a class="iref" href="#rfc.xref.header.transfer-encoding.3">4.4</a>, <a class="iref" href="#rfc.xref.header.transfer-encoding.4">4.5</a>, <a class="iref" href="#rfc.iref.h.8"><b>8.7</b></a>, <a class="iref" href="#rfc.xref.header.transfer-encoding.5">9.1</a></li>
     
    28982899                     </ul>
    28992900                  </li>
    2900                   <li class="indline1">Host header&nbsp;&nbsp;<a class="iref" href="#rfc.iref.h.4"><b>8.4</b></a>, <a class="iref" href="#rfc.xref.header.host.1">9.1</a>, <a class="iref" href="#rfc.xref.header.host.2">D.1.1</a></li>
     2901                  <li class="indline1">Host header&nbsp;&nbsp;<a class="iref" href="#rfc.iref.h.4"><b>8.4</b></a>, <a class="iref" href="#rfc.xref.header.host.1">9.1</a>, <a class="iref" href="#rfc.xref.header.host.2">C.1.1</a></li>
    29012902               </ul>
    29022903            </li>
     
    29102911                  <li class="indline1">Media Type&nbsp;&nbsp;
    29112912                     <ul class="ind">
    2912                         <li class="indline1">application/http&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.4"><b>A.2</b></a></li>
    2913                         <li class="indline1">message/http&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.2"><b>A.1</b></a></li>
     2913                        <li class="indline1">application/http&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.4"><b>9.2.2</b></a></li>
     2914                        <li class="indline1">message/http&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.2"><b>9.2.1</b></a></li>
    29142915                     </ul>
    29152916                  </li>
    29162917                  <li class="indline1">message&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.1">1.3</a></li>
    2917                   <li class="indline1">message/http Media Type&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.3"><b>A.1</b></a></li>
     2918                  <li class="indline1">message/http Media Type&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.3"><b>9.2.1</b></a></li>
    29182919               </ul>
    29192920            </li>
    29202921            <li class="indline0"><a id="rfc.index.N" href="#rfc.index.N"><b>N</b></a><ul class="ind">
    2921                   <li class="indline1"><em>Nie1997</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Nie1997.1">7.1.1</a>, <a class="iref" href="#Nie1997"><b>12.2</b></a>, <a class="iref" href="#rfc.xref.Nie1997.2">D.3</a></li>
     2922                  <li class="indline1"><em>Nie1997</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Nie1997.1">7.1.1</a>, <a class="iref" href="#Nie1997"><b>12.2</b></a>, <a class="iref" href="#rfc.xref.Nie1997.2">C.3</a></li>
    29222923               </ul>
    29232924            </li>
     
    29422943                     </ul>
    29432944                  </li>
    2944                   <li class="indline1"><em>Part3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.1">1.3</a>, <a class="iref" href="#rfc.xref.Part3.2">1.3</a>, <a class="iref" href="#rfc.xref.Part3.3">1.3</a>, <a class="iref" href="#rfc.xref.Part3.4">1.4</a>, <a class="iref" href="#rfc.xref.Part3.5">2.2</a>, <a class="iref" href="#rfc.xref.Part3.6">2.3</a>, <a class="iref" href="#rfc.xref.Part3.7">2.3</a>, <a class="iref" href="#rfc.xref.Part3.8">2.3</a>, <a class="iref" href="#rfc.xref.Part3.9">3.4</a>, <a class="iref" href="#rfc.xref.Part3.10">3.4</a>, <a class="iref" href="#rfc.xref.Part3.11">4.2</a>, <a class="iref" href="#rfc.xref.Part3.12">5</a>, <a class="iref" href="#rfc.xref.Part3.13">6</a>, <a class="iref" href="#rfc.xref.Part3.14">8.5</a>, <a class="iref" href="#Part3"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.Part3.15">B</a>, <a class="iref" href="#rfc.xref.Part3.16">D.3</a><ul class="ind">
     2945                  <li class="indline1"><em>Part3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.1">1.3</a>, <a class="iref" href="#rfc.xref.Part3.2">1.3</a>, <a class="iref" href="#rfc.xref.Part3.3">1.3</a>, <a class="iref" href="#rfc.xref.Part3.4">1.4</a>, <a class="iref" href="#rfc.xref.Part3.5">2.2</a>, <a class="iref" href="#rfc.xref.Part3.6">2.3</a>, <a class="iref" href="#rfc.xref.Part3.7">2.3</a>, <a class="iref" href="#rfc.xref.Part3.8">2.3</a>, <a class="iref" href="#rfc.xref.Part3.9">3.4</a>, <a class="iref" href="#rfc.xref.Part3.10">3.4</a>, <a class="iref" href="#rfc.xref.Part3.11">4.2</a>, <a class="iref" href="#rfc.xref.Part3.12">5</a>, <a class="iref" href="#rfc.xref.Part3.13">6</a>, <a class="iref" href="#rfc.xref.Part3.14">8.5</a>, <a class="iref" href="#Part3"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.Part3.15">A</a>, <a class="iref" href="#rfc.xref.Part3.16">C.3</a><ul class="ind">
    29452946                        <li class="indline1"><em>Section 3.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.9">3.4</a>, <a class="iref" href="#rfc.xref.Part3.10">3.4</a></li>
    29462947                        <li class="indline1"><em>Section 3.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.5">2.2</a></li>
     
    29542955                     </ul>
    29552956                  </li>
    2956                   <li class="indline1"><em>Part5</em>&nbsp;&nbsp;<a class="iref" href="#Part5"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.Part5.1">D.3</a></li>
    2957                   <li class="indline1"><em>Part6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.1">1.3</a>, <a class="iref" href="#rfc.xref.Part6.2">1.4</a>, <a class="iref" href="#rfc.xref.Part6.3">2.3</a>, <a class="iref" href="#rfc.xref.Part6.4">2.3</a>, <a class="iref" href="#rfc.xref.Part6.5">2.3</a>, <a class="iref" href="#rfc.xref.Part6.6">4.5</a>, <a class="iref" href="#rfc.xref.Part6.7">4.5</a>, <a class="iref" href="#rfc.xref.Part6.8">4.5</a>, <a class="iref" href="#Part6"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.Part6.9">D.3</a><ul class="ind">
     2957                  <li class="indline1"><em>Part5</em>&nbsp;&nbsp;<a class="iref" href="#Part5"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.Part5.1">C.3</a></li>
     2958                  <li class="indline1"><em>Part6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.1">1.3</a>, <a class="iref" href="#rfc.xref.Part6.2">1.4</a>, <a class="iref" href="#rfc.xref.Part6.3">2.3</a>, <a class="iref" href="#rfc.xref.Part6.4">2.3</a>, <a class="iref" href="#rfc.xref.Part6.5">2.3</a>, <a class="iref" href="#rfc.xref.Part6.6">4.5</a>, <a class="iref" href="#rfc.xref.Part6.7">4.5</a>, <a class="iref" href="#rfc.xref.Part6.8">4.5</a>, <a class="iref" href="#Part6"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.Part6.9">C.3</a><ul class="ind">
    29582959                        <li class="indline1"><em>Section 1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.1">1.3</a>, <a class="iref" href="#rfc.xref.Part6.2">1.4</a></li>
    29592960                        <li class="indline1"><em>Section 16.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.6">4.5</a></li>
     
    29812982                  <li class="indline1"><em>RFC2045</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2045.1">1.1</a>, <a class="iref" href="#rfc.xref.RFC2045.2">3.4</a>, <a class="iref" href="#rfc.xref.RFC2045.3">11</a>, <a class="iref" href="#RFC2045"><b>12.1</b></a></li>
    29822983                  <li class="indline1"><em>RFC2047</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2047.1">2.2</a>, <a class="iref" href="#RFC2047"><b>12.1</b></a></li>
    2983                   <li class="indline1"><em>RFC2068</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2068.1">3.1</a>, <a class="iref" href="#rfc.xref.RFC2068.2">7.1.1</a>, <a class="iref" href="#rfc.xref.RFC2068.3">7.1.3</a>, <a class="iref" href="#rfc.xref.RFC2068.4">7.2.3</a>, <a class="iref" href="#rfc.xref.RFC2068.5">11</a>, <a class="iref" href="#RFC2068"><b>12.2</b></a>, <a class="iref" href="#rfc.xref.RFC2068.6">D</a>, <a class="iref" href="#rfc.xref.RFC2068.7">D.2</a><ul class="ind">
    2984                         <li class="indline1"><em>Section 19.7.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2068.6">D</a></li>
     2984                  <li class="indline1"><em>RFC2068</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2068.1">3.1</a>, <a class="iref" href="#rfc.xref.RFC2068.2">7.1.1</a>, <a class="iref" href="#rfc.xref.RFC2068.3">7.1.3</a>, <a class="iref" href="#rfc.xref.RFC2068.4">7.2.3</a>, <a class="iref" href="#rfc.xref.RFC2068.5">11</a>, <a class="iref" href="#RFC2068"><b>12.2</b></a>, <a class="iref" href="#rfc.xref.RFC2068.6">C</a>, <a class="iref" href="#rfc.xref.RFC2068.7">C.2</a><ul class="ind">
     2985                        <li class="indline1"><em>Section 19.7.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2068.6">C</a></li>
    29852986                     </ul>
    29862987                  </li>
    2987                   <li class="indline1"><em>RFC2119</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2119.1">1.2</a>, <a class="iref" href="#RFC2119"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.RFC2119.2">D.3</a></li>
    2988                   <li class="indline1"><em>RFC2145</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2145.1">3.1</a>, <a class="iref" href="#rfc.xref.RFC2145.2">3.1</a>, <a class="iref" href="#RFC2145"><b>12.2</b></a>, <a class="iref" href="#rfc.xref.RFC2145.3">D.3</a></li>
     2988                  <li class="indline1"><em>RFC2119</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2119.1">1.2</a>, <a class="iref" href="#RFC2119"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.RFC2119.2">C.3</a></li>
     2989                  <li class="indline1"><em>RFC2145</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2145.1">3.1</a>, <a class="iref" href="#rfc.xref.RFC2145.2">3.1</a>, <a class="iref" href="#RFC2145"><b>12.2</b></a>, <a class="iref" href="#rfc.xref.RFC2145.3">C.3</a></li>
    29892990                  <li class="indline1"><em>RFC2324</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2324.1">1.1</a>, <a class="iref" href="#RFC2324"><b>12.2</b></a></li>
    2990                   <li class="indline1"><em>RFC2396</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2396.1">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.2">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.3">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.4">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.5">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.6">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.7">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.8">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.9">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.10">3.2.3</a>, <a class="iref" href="#rfc.xref.RFC2396.11">5.1.2</a>, <a class="iref" href="#RFC2396"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.RFC2396.12">D.4</a><ul class="ind">
     2991                  <li class="indline1"><em>RFC2396</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2396.1">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.2">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.3">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.4">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.5">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.6">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.7">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.8">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.9">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.10">3.2.3</a>, <a class="iref" href="#rfc.xref.RFC2396.11">5.1.2</a>, <a class="iref" href="#RFC2396"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.RFC2396.12">C.4</a><ul class="ind">
    29912992                        <li class="indline1"><em>Section 3.2.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2396.6">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.9">3.2.1</a></li>
    29922993                        <li class="indline1"><em>Section 3.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2396.3">3.2.1</a></li>
    29932994                        <li class="indline1"><em>Section 3.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2396.7">3.2.1</a></li>
    2994                         <li class="indline1"><em>Section 3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2396.2">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.5">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.12">D.4</a></li>
     2995                        <li class="indline1"><em>Section 3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2396.2">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.5">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.12">C.4</a></li>
    29952996                        <li class="indline1"><em>Section 4.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2396.4">3.2.1</a></li>
    29962997                        <li class="indline1"><em>Section 5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2396.8">3.2.1</a></li>
    29972998                     </ul>
    29982999                  </li>
    2999                   <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#rfc.xref.RFC2616.2">1</a>, <a class="iref" href="#rfc.xref.RFC2616.3">11</a>, <a class="iref" href="#RFC2616"><b>12.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.4">E.1</a></li>
     3000                  <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#rfc.xref.RFC2616.2">1</a>, <a class="iref" href="#rfc.xref.RFC2616.3">11</a>, <a class="iref" href="#RFC2616"><b>12.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.4">D.1</a></li>
    30003001                  <li class="indline1"><em>RFC2821</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2821.1">1.1</a>, <a class="iref" href="#RFC2821"><b>12.2</b></a></li>
    30013002                  <li class="indline1"><em>RFC2822</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2822.1">1.1</a>, <a class="iref" href="#rfc.xref.RFC2822.2">4.1</a>, <a class="iref" href="#rfc.xref.RFC2822.3">4.2</a>, <a class="iref" href="#rfc.xref.RFC2822.4">8.3</a>, <a class="iref" href="#rfc.xref.RFC2822.5">8.9</a>, <a class="iref" href="#RFC2822"><b>12.2</b></a><ul class="ind">
     
    30073008                  <li class="indline1"><em>RFC3864</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3864.1">9.1</a>, <a class="iref" href="#RFC3864"><b>12.2</b></a></li>
    30083009                  <li class="indline1"><em>RFC3977</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3977.1">1.1</a>, <a class="iref" href="#RFC3977"><b>12.2</b></a></li>
    3009                   <li class="indline1"><em>RFC4288</em>&nbsp;&nbsp;<a class="iref" href="#RFC4288"><b>12.2</b></a>, <a class="iref" href="#rfc.xref.RFC4288.1">A</a></li>
     3010                  <li class="indline1"><em>RFC4288</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC4288.1">9.2</a>, <a class="iref" href="#RFC4288"><b>12.2</b></a></li>
    30103011                  <li class="indline1"><em>RFC822</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC822.1">3.3.1</a>, <a class="iref" href="#RFC822"><b>12.2</b></a></li>
    30113012                  <li class="indline1"><em>RFC822ABNF</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC822ABNF.1">2.1</a>, <a class="iref" href="#rfc.xref.RFC822ABNF.2">11</a>, <a class="iref" href="#RFC822ABNF"><b>12.1</b></a></li>
     
    30193020            </li>
    30203021            <li class="indline0"><a id="rfc.index.T" href="#rfc.index.T"><b>T</b></a><ul class="ind">
    3021                   <li class="indline1">TE header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.te.1">3.4</a>, <a class="iref" href="#rfc.xref.header.te.2">3.4.1</a>, <a class="iref" href="#rfc.iref.t.2"><b>8.5</b></a>, <a class="iref" href="#rfc.xref.header.te.3">9.1</a>, <a class="iref" href="#rfc.xref.header.te.4">D.3</a></li>
     3022                  <li class="indline1">TE header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.te.1">3.4</a>, <a class="iref" href="#rfc.xref.header.te.2">3.4.1</a>, <a class="iref" href="#rfc.iref.t.2"><b>8.5</b></a>, <a class="iref" href="#rfc.xref.header.te.3">9.1</a>, <a class="iref" href="#rfc.xref.header.te.4">C.3</a></li>
    30223023                  <li class="indline1"><em>Tou1998</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Tou1998.1">7.1.1</a>, <a class="iref" href="#Tou1998"><b>12.2</b></a></li>
    30233024                  <li class="indline1">Trailer header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.trailer.1">3.4.1</a>, <a class="iref" href="#rfc.xref.header.trailer.2">4.5</a>, <a class="iref" href="#rfc.iref.t.3"><b>8.6</b></a>, <a class="iref" href="#rfc.xref.header.trailer.3">9.1</a></li>
Note: See TracChangeset for help on using the changeset viewer.