![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Changeset 385 for draft-ietf-httpbis
- Timestamp:
- Nov 14, 2008, 12:26:21 PM (11 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 4 edited
-
p1-messaging.html (modified) (47 diffs)
-
p1-messaging.xml (modified) (2 diffs)
-
p3-payload.html (modified) (7 diffs)
-
p3-payload.xml (modified) (3 diffs)
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r384 r385 377 377 <link rel="Chapter" href="#rfc.section.12" title="12 References"> 378 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 Terminology" href="#rfc.section.D"> 382 <link rel="Appendix" title="E Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.E"> 379 <link rel="Appendix" title="B Compatibility with Previous Versions" href="#rfc.section.B"> 380 <link rel="Appendix" title="C Terminology" href="#rfc.section.C"> 381 <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D"> 383 382 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.400, 2008-10-10 14:04:14, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 384 383 <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> … … 510 509 list is at <<a href="http://tools.ietf.org/wg/httpbis/trac/report/11">http://tools.ietf.org/wg/httpbis/trac/report/11</a>> and related documents (including fancy diffs) can be found at <<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>>. 511 510 </p> 512 <p>The changes in this draft are summarized in <a href="#changes.since.05" title="Since draft-ietf-httpbis-p1-messaging-05">Appendix E.7</a>.511 <p>The changes in this draft are summarized in <a href="#changes.since.05" title="Since draft-ietf-httpbis-p1-messaging-05">Appendix D.7</a>. 513 512 </p> 514 513 <hr class="noprint"> … … 631 630 <li class="tocline0"><a href="#rfc.authors">Authors' Addresses</a></li> 632 631 <li class="tocline0">A. <a href="#tolerant.applications">Tolerant Applications</a></li> 633 <li class="tocline0">B. <a href="#conversion.of.date.formats">Conversion of Date Formats</a></li> 634 <li class="tocline0">C. <a href="#compatibility">Compatibility with Previous Versions</a><ul class="toc"> 635 <li class="tocline1">C.1 <a href="#changes.from.1.0">Changes from HTTP/1.0</a><ul class="toc"> 636 <li class="tocline1">C.1.1 <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> 632 <li class="tocline0">B. <a href="#compatibility">Compatibility with Previous Versions</a><ul class="toc"> 633 <li class="tocline1">B.1 <a href="#changes.from.1.0">Changes from HTTP/1.0</a><ul class="toc"> 634 <li class="tocline1">B.1.1 <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> 637 635 </ul> 638 636 </li> 639 <li class="tocline1"> C.2 <a href="#compatibility.with.http.1.0.persistent.connections">Compatibility with HTTP/1.0 Persistent Connections</a></li>640 <li class="tocline1"> C.3 <a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li>641 <li class="tocline1"> C.4 <a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>637 <li class="tocline1">B.2 <a href="#compatibility.with.http.1.0.persistent.connections">Compatibility with HTTP/1.0 Persistent Connections</a></li> 638 <li class="tocline1">B.3 <a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li> 639 <li class="tocline1">B.4 <a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li> 642 640 </ul> 643 641 </li> 644 <li class="tocline0"> D. <a href="#terminology">Terminology</a></li>645 <li class="tocline0"> E. <a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc">646 <li class="tocline1"> E.1 <a href="#rfc.section.E.1">Since RFC2616</a></li>647 <li class="tocline1"> E.2 <a href="#rfc.section.E.2">Since draft-ietf-httpbis-p1-messaging-00</a></li>648 <li class="tocline1"> E.3 <a href="#rfc.section.E.3">Since draft-ietf-httpbis-p1-messaging-01</a></li>649 <li class="tocline1"> E.4 <a href="#changes.since.02">Since draft-ietf-httpbis-p1-messaging-02</a></li>650 <li class="tocline1"> E.5 <a href="#changes.since.03">Since draft-ietf-httpbis-p1-messaging-03</a></li>651 <li class="tocline1"> E.6 <a href="#changes.since.04">Since draft-ietf-httpbis-p1-messaging-04</a></li>652 <li class="tocline1"> E.7 <a href="#changes.since.05">Since draft-ietf-httpbis-p1-messaging-05</a></li>642 <li class="tocline0">C. <a href="#terminology">Terminology</a></li> 643 <li class="tocline0">D. <a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc"> 644 <li class="tocline1">D.1 <a href="#rfc.section.D.1">Since RFC2616</a></li> 645 <li class="tocline1">D.2 <a href="#rfc.section.D.2">Since draft-ietf-httpbis-p1-messaging-00</a></li> 646 <li class="tocline1">D.3 <a href="#rfc.section.D.3">Since draft-ietf-httpbis-p1-messaging-01</a></li> 647 <li class="tocline1">D.4 <a href="#changes.since.02">Since draft-ietf-httpbis-p1-messaging-02</a></li> 648 <li class="tocline1">D.5 <a href="#changes.since.03">Since draft-ietf-httpbis-p1-messaging-03</a></li> 649 <li class="tocline1">D.6 <a href="#changes.since.04">Since draft-ietf-httpbis-p1-messaging-04</a></li> 650 <li class="tocline1">D.7 <a href="#changes.since.05">Since draft-ietf-httpbis-p1-messaging-05</a></li> 653 651 </ul> 654 652 </li> … … 1304 1302 <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a> <a id="the.resource.identified.by.a.request" href="#the.resource.identified.by.a.request">The Resource Identified by a Request</a></h2> 1305 1303 <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> 1306 <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 C.1.1</a> for other requirements on Host support in HTTP/1.1.)1304 <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 B.1.1</a> for other requirements on Host support in HTTP/1.1.) 1307 1305 </p> 1308 1306 <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 … … 1398 1396 connection. 1399 1397 </p> 1400 <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 C.2</a> for more information on backward compatibility with HTTP/1.0 clients.1398 <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 B.2</a> for more information on backward compatibility with HTTP/1.0 clients. 1401 1399 </p> 1402 1400 <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 4.4</a>. … … 1564 1562 </p> 1565 1563 <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 1566 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 C.2</a>.1564 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 B.2</a>. 1567 1565 </p> 1568 1566 <div id="rfc.iref.c.2"></div> … … 1640 1638 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. 1641 1639 </p> 1642 <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.1640 <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">B.1.1</a> for other requirements relating to Host. 1643 1641 </p> 1644 1642 <div id="rfc.iref.t.1"></div> … … 2317 2315 </li> 2318 2316 </ul> 2319 <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a id="conversion.of.date.formats" href="#conversion.of.date.formats">Conversion of Date Formats</a></h1> 2320 <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 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. 2321 </p> 2322 <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a> <a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1> 2323 <p id="rfc.section.C.p.1">HTTP has been in use by the World-Wide Web global information initiative since 1990. The first version of HTTP, later referred 2317 <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1> 2318 <p id="rfc.section.B.p.1">HTTP has been in use by the World-Wide Web global information initiative since 1990. The first version of HTTP, later referred 2324 2319 to as HTTP/0.9, was a simple protocol for hypertext data transfer across the Internet with only a single method and no metadata. 2325 2320 HTTP/1.0, as defined by <a href="#RFC1945" id="rfc.xref.RFC1945.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.0">[RFC1945]</cite></a>, added a range of request methods and MIME-like messaging that could include metadata about the data transferred and modifiers … … 2329 2324 to determine each other's true capabilities. 2330 2325 </p> 2331 <p id="rfc.section. C.p.2">HTTP/1.1 remains compatible with HTTP/1.0 by including more stringent requirements that enable reliable implementations, adding2326 <p id="rfc.section.B.p.2">HTTP/1.1 remains compatible with HTTP/1.0 by including more stringent requirements that enable reliable implementations, adding 2332 2327 only those new features that will either be safely ignored by an HTTP/1.0 recipient or only sent when communicating with a 2333 2328 party advertising compliance with HTTP/1.1. 2334 2329 </p> 2335 <p id="rfc.section. C.p.3">It is beyond the scope of a protocol specification to mandate compliance with previous versions. HTTP/1.1 was deliberately2330 <p id="rfc.section.B.p.3">It is beyond the scope of a protocol specification to mandate compliance with previous versions. HTTP/1.1 was deliberately 2336 2331 designed, however, to make supporting previous versions easy. It is worth noting that, at the time of composing this specification 2337 2332 (1996), we would expect commercial HTTP/1.1 servers to: … … 2342 2337 <li>respond appropriately with a message in the same major version used by the client.</li> 2343 2338 </ul> 2344 <p id="rfc.section. C.p.4">And we would expect HTTP/1.1 clients to: </p>2339 <p id="rfc.section.B.p.4">And we would expect HTTP/1.1 clients to: </p> 2345 2340 <ul> 2346 2341 <li>recognize the format of the Status-Line for HTTP/1.0 and 1.1 responses;</li> 2347 2342 <li>understand any valid response in the format of HTTP/0.9, 1.0, or 1.1.</li> 2348 2343 </ul> 2349 <p id="rfc.section. C.p.5">For most implementations of HTTP/1.0, each connection is established by the client prior to the request and closed by the2344 <p id="rfc.section.B.p.5">For most implementations of HTTP/1.0, each connection is established by the client prior to the request and closed by the 2350 2345 server after sending the response. Some implementations implement the Keep-Alive version of persistent connections described 2351 2346 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>. 2352 2347 </p> 2353 <h2 id="rfc.section. C.1"><a href="#rfc.section.C.1">C.1</a> <a id="changes.from.1.0" href="#changes.from.1.0">Changes from HTTP/1.0</a></h2>2354 <p id="rfc.section. C.1.p.1">This section summarizes major differences between versions HTTP/1.0 and HTTP/1.1.</p>2355 <h3 id="rfc.section. C.1.1"><a href="#rfc.section.C.1.1">C.1.1</a> <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>2356 <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 8.4</a>) is missing from an HTTP/1.1 request, and accept absolute URIs (<a href="#request-uri" title="Request-URI">Section 5.1.2</a>) are among the most important changes defined by this specification.2357 </p> 2358 <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 mechanism2348 <h2 id="rfc.section.B.1"><a href="#rfc.section.B.1">B.1</a> <a id="changes.from.1.0" href="#changes.from.1.0">Changes from HTTP/1.0</a></h2> 2349 <p id="rfc.section.B.1.p.1">This section summarizes major differences between versions HTTP/1.0 and HTTP/1.1.</p> 2350 <h3 id="rfc.section.B.1.1"><a href="#rfc.section.B.1.1">B.1.1</a> <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> 2351 <p id="rfc.section.B.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 8.4</a>) is missing from an HTTP/1.1 request, and accept absolute URIs (<a href="#request-uri" title="Request-URI">Section 5.1.2</a>) are among the most important changes defined by this specification. 2352 </p> 2353 <p id="rfc.section.B.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 2359 2354 for distinguishing the intended server of a request than the IP address to which that request was directed. The changes outlined 2360 2355 above will allow the Internet, once older HTTP clients are no longer common, to support multiple Web sites from a single IP … … 2375 2370 </li> 2376 2371 </ul> 2377 <h2 id="rfc.section. C.2"><a href="#rfc.section.C.2">C.2</a> <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>2378 <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.02372 <h2 id="rfc.section.B.2"><a href="#rfc.section.B.2">B.2</a> <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> 2373 <p id="rfc.section.B.2.p.1">Some clients and servers might wish to be compatible with some previous implementations of persistent connections in HTTP/1.0 2379 2374 clients and servers. Persistent connections in HTTP/1.0 are explicitly negotiated as they are not the default behavior. HTTP/1.0 2380 2375 experimental implementations of persistent connections are faulty, and the new facilities in HTTP/1.1 are designed to rectify … … 2384 2379 from using Keep-Alive when talking to proxies. 2385 2380 </p> 2386 <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.2381 <p id="rfc.section.B.2.p.2">However, talking to proxies is the most important use of persistent connections, so that prohibition is clearly unacceptable. 2387 2382 Therefore, we need some other mechanism for indicating a persistent connection is desired, which is safe to use even when 2388 2383 talking to an old proxy that ignores Connection. Persistent connections are the default for HTTP/1.1 messages; we introduce 2389 2384 a new keyword (Connection: close) for declaring non-persistence. See <a href="#header.connection" id="rfc.xref.header.connection.7" title="Connection">Section 8.1</a>. 2390 2385 </p> 2391 <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>.2392 </p> 2393 <h2 id="rfc.section. C.3"><a href="#rfc.section.C.3">C.3</a> <a id="changes.from.rfc.2068" href="#changes.from.rfc.2068">Changes from RFC 2068</a></h2>2394 <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 respect2386 <p id="rfc.section.B.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>. 2387 </p> 2388 <h2 id="rfc.section.B.3"><a href="#rfc.section.B.3">B.3</a> <a id="changes.from.rfc.2068" href="#changes.from.rfc.2068">Changes from RFC 2068</a></h2> 2389 <p id="rfc.section.B.3.p.1">This specification has been carefully audited to correct and disambiguate key word usage; RFC 2068 had many problems in respect 2395 2390 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>. 2396 2391 </p> 2397 <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 allow2392 <p id="rfc.section.B.3.p.2">Transfer-coding and message lengths all interact in ways that required fixing exactly when chunked encoding is used (to allow 2398 2393 for transfer encoding that may not be self delimiting); it was important to straighten out exactly how message lengths are 2399 2394 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.14"><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.8"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) 2400 2395 </p> 2401 <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.02396 <p id="rfc.section.B.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 2402 2397 implementations (<a href="#http.version" title="HTTP Version">Section 3.1</a>) 2403 2398 </p> 2404 <p id="rfc.section. C.3.p.4">Transfer-coding had significant problems, particularly with interactions with chunked encoding. The solution is that transfer-codings2399 <p id="rfc.section.B.3.p.4">Transfer-coding had significant problems, particularly with interactions with chunked encoding. The solution is that transfer-codings 2405 2400 become as full fledged as content-codings. This involves adding an IANA registry for transfer-codings (separate from content 2406 2401 codings), a new header field (TE) and enabling trailer headers in the future. Transfer encoding is a major performance benefit, … … 2408 2403 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>) 2409 2404 </p> 2410 <h2 id="rfc.section. C.4"><a href="#rfc.section.C.4">C.4</a> <a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>2411 <p id="rfc.section. C.4.p.1">Rules about implicit linear white space between certain grammar productions have been removed; now it's only allowed when2405 <h2 id="rfc.section.B.4"><a href="#rfc.section.B.4">B.4</a> <a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2> 2406 <p id="rfc.section.B.4.p.1">Rules about implicit linear white space between certain grammar productions have been removed; now it's only allowed when 2412 2407 specifically pointed out in the ABNF. The CHAR rule does not allow the NUL character anymore (this affects the comment and 2413 2408 quoted-string rules). Furthermore, the quoted-pair rule does not allow escaping NUL, CR or LF anymore. (<a href="#basic.rules" title="Basic Rules">Section 2.2</a>) 2414 2409 </p> 2415 <p id="rfc.section. C.4.p.2">Clarify that HTTP-Version is case sensitive. (<a href="#http.version" title="HTTP Version">Section 3.1</a>)2416 </p> 2417 <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>)2418 </p> 2419 <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 3.4.1</a>)2420 </p> 2421 <p id="rfc.section. C.4.p.5">Update use of abs_path production from RFC1808 to the path-absolute + query components of RFC3986. (<a href="#request-uri" title="Request-URI">Section 5.1.2</a>)2422 </p> 2423 <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 8.1</a>)2424 </p> 2425 <h1 id="rfc.section. D"><a href="#rfc.section.D">D.</a> <a id="terminology" href="#terminology">Terminology</a></h1>2426 <p id="rfc.section. D.p.1">This specification uses a number of terms to refer to the roles played by participants in, and objects of, the HTTP communication.</p>2427 <p id="rfc.section. D.p.2"> <span id="rfc.iref.c.3"></span> <dfn>connection</dfn>2410 <p id="rfc.section.B.4.p.2">Clarify that HTTP-Version is case sensitive. (<a href="#http.version" title="HTTP Version">Section 3.1</a>) 2411 </p> 2412 <p id="rfc.section.B.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>) 2413 </p> 2414 <p id="rfc.section.B.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 3.4.1</a>) 2415 </p> 2416 <p id="rfc.section.B.4.p.5">Update use of abs_path production from RFC1808 to the path-absolute + query components of RFC3986. (<a href="#request-uri" title="Request-URI">Section 5.1.2</a>) 2417 </p> 2418 <p id="rfc.section.B.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 8.1</a>) 2419 </p> 2420 <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a> <a id="terminology" href="#terminology">Terminology</a></h1> 2421 <p id="rfc.section.C.p.1">This specification uses a number of terms to refer to the roles played by participants in, and objects of, the HTTP communication.</p> 2422 <p id="rfc.section.C.p.2"> <span id="rfc.iref.c.3"></span> <dfn>connection</dfn> 2428 2423 </p> 2429 2424 <dl class="empty"> 2430 2425 <dd>A transport layer virtual circuit established between two programs for the purpose of communication.</dd> 2431 2426 </dl> 2432 <p id="rfc.section. D.p.3"> <span id="rfc.iref.m.4"></span> <dfn>message</dfn>2427 <p id="rfc.section.C.p.3"> <span id="rfc.iref.m.4"></span> <dfn>message</dfn> 2433 2428 </p> 2434 2429 <dl class="empty"> … … 2436 2431 </dd> 2437 2432 </dl> 2438 <p id="rfc.section. D.p.4"> <span id="rfc.iref.r.1"></span> <dfn>request</dfn>2433 <p id="rfc.section.C.p.4"> <span id="rfc.iref.r.1"></span> <dfn>request</dfn> 2439 2434 </p> 2440 2435 <dl class="empty"> … … 2442 2437 </dd> 2443 2438 </dl> 2444 <p id="rfc.section. D.p.5"> <span id="rfc.iref.r.2"></span> <dfn>response</dfn>2439 <p id="rfc.section.C.p.5"> <span id="rfc.iref.r.2"></span> <dfn>response</dfn> 2445 2440 </p> 2446 2441 <dl class="empty"> … … 2448 2443 </dd> 2449 2444 </dl> 2450 <p id="rfc.section. D.p.6"> <span id="rfc.iref.r.3"></span> <dfn>resource</dfn>2445 <p id="rfc.section.C.p.6"> <span id="rfc.iref.r.3"></span> <dfn>resource</dfn> 2451 2446 </p> 2452 2447 <dl class="empty"> … … 2455 2450 </dd> 2456 2451 </dl> 2457 <p id="rfc.section. D.p.7"> <span id="rfc.iref.e.1"></span> <dfn>entity</dfn>2452 <p id="rfc.section.C.p.7"> <span id="rfc.iref.e.1"></span> <dfn>entity</dfn> 2458 2453 </p> 2459 2454 <dl class="empty"> … … 2462 2457 </dd> 2463 2458 </dl> 2464 <p id="rfc.section. D.p.8"> <span id="rfc.iref.r.4"></span> <dfn>representation</dfn>2459 <p id="rfc.section.C.p.8"> <span id="rfc.iref.r.4"></span> <dfn>representation</dfn> 2465 2460 </p> 2466 2461 <dl class="empty"> … … 2468 2463 </dd> 2469 2464 </dl> 2470 <p id="rfc.section. D.p.9"> <span id="rfc.iref.c.4"></span> <dfn>content negotiation</dfn>2465 <p id="rfc.section.C.p.9"> <span id="rfc.iref.c.4"></span> <dfn>content negotiation</dfn> 2471 2466 </p> 2472 2467 <dl class="empty"> … … 2474 2469 </dd> 2475 2470 </dl> 2476 <p id="rfc.section. D.p.10"> <span id="rfc.iref.v.2"></span> <dfn>variant</dfn>2471 <p id="rfc.section.C.p.10"> <span id="rfc.iref.v.2"></span> <dfn>variant</dfn> 2477 2472 </p> 2478 2473 <dl class="empty"> … … 2481 2476 </dd> 2482 2477 </dl> 2483 <p id="rfc.section. D.p.11"> <span id="rfc.iref.c.5"></span> <dfn>client</dfn>2478 <p id="rfc.section.C.p.11"> <span id="rfc.iref.c.5"></span> <dfn>client</dfn> 2484 2479 </p> 2485 2480 <dl class="empty"> 2486 2481 <dd>A program that establishes connections for the purpose of sending requests.</dd> 2487 2482 </dl> 2488 <p id="rfc.section. D.p.12"> <span id="rfc.iref.u.4"></span> <dfn>user agent</dfn>2483 <p id="rfc.section.C.p.12"> <span id="rfc.iref.u.4"></span> <dfn>user agent</dfn> 2489 2484 </p> 2490 2485 <dl class="empty"> … … 2493 2488 </dd> 2494 2489 </dl> 2495 <p id="rfc.section. D.p.13"> <span id="rfc.iref.s.1"></span> <dfn>server</dfn>2490 <p id="rfc.section.C.p.13"> <span id="rfc.iref.s.1"></span> <dfn>server</dfn> 2496 2491 </p> 2497 2492 <dl class="empty"> … … 2502 2497 </dd> 2503 2498 </dl> 2504 <p id="rfc.section. D.p.14"> <span id="rfc.iref.o.1"></span> <dfn>origin server</dfn>2499 <p id="rfc.section.C.p.14"> <span id="rfc.iref.o.1"></span> <dfn>origin server</dfn> 2505 2500 </p> 2506 2501 <dl class="empty"> 2507 2502 <dd>The server on which a given resource resides or is to be created.</dd> 2508 2503 </dl> 2509 <p id="rfc.section. D.p.15"> <span id="rfc.iref.p.1"></span> <dfn>proxy</dfn>2504 <p id="rfc.section.C.p.15"> <span id="rfc.iref.p.1"></span> <dfn>proxy</dfn> 2510 2505 </p> 2511 2506 <dl class="empty"> … … 2518 2513 </dd> 2519 2514 </dl> 2520 <p id="rfc.section. D.p.16"> <span id="rfc.iref.g.97"></span> <dfn>gateway</dfn>2515 <p id="rfc.section.C.p.16"> <span id="rfc.iref.g.97"></span> <dfn>gateway</dfn> 2521 2516 </p> 2522 2517 <dl class="empty"> … … 2525 2520 </dd> 2526 2521 </dl> 2527 <p id="rfc.section. D.p.17"> <span id="rfc.iref.t.4"></span> <dfn>tunnel</dfn>2522 <p id="rfc.section.C.p.17"> <span id="rfc.iref.t.4"></span> <dfn>tunnel</dfn> 2528 2523 </p> 2529 2524 <dl class="empty"> … … 2533 2528 </dd> 2534 2529 </dl> 2535 <p id="rfc.section. D.p.18"> <span id="rfc.iref.c.6"></span> <dfn>cache</dfn>2530 <p id="rfc.section.C.p.18"> <span id="rfc.iref.c.6"></span> <dfn>cache</dfn> 2536 2531 </p> 2537 2532 <dl class="empty"> … … 2541 2536 </dd> 2542 2537 </dl> 2543 <p id="rfc.section. D.p.19"> <span id="rfc.iref.c.7"></span> <dfn>cacheable</dfn>2538 <p id="rfc.section.C.p.19"> <span id="rfc.iref.c.7"></span> <dfn>cacheable</dfn> 2544 2539 </p> 2545 2540 <dl class="empty"> … … 2549 2544 </dd> 2550 2545 </dl> 2551 <p id="rfc.section. D.p.20"> <span id="rfc.iref.u.5"></span> <span id="rfc.iref.d.2"></span> <dfn>upstream</dfn>/<dfn>downstream</dfn>2546 <p id="rfc.section.C.p.20"> <span id="rfc.iref.u.5"></span> <span id="rfc.iref.d.2"></span> <dfn>upstream</dfn>/<dfn>downstream</dfn> 2552 2547 </p> 2553 2548 <dl class="empty"> 2554 2549 <dd>Upstream and downstream describe the flow of a message: all messages flow from upstream to downstream.</dd> 2555 2550 </dl> 2556 <p id="rfc.section. D.p.21"> <span id="rfc.iref.i.1"></span> <span id="rfc.iref.o.2"></span> <dfn>inbound</dfn>/<dfn>outbound</dfn>2551 <p id="rfc.section.C.p.21"> <span id="rfc.iref.i.1"></span> <span id="rfc.iref.o.2"></span> <dfn>inbound</dfn>/<dfn>outbound</dfn> 2557 2552 </p> 2558 2553 <dl class="empty"> … … 2561 2556 </dd> 2562 2557 </dl> 2563 <h1 id="rfc.section. E"><a href="#rfc.section.E">E.</a> <a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>2564 <h2 id="rfc.section. E.1"><a href="#rfc.section.E.1">E.1</a> Since RFC26162558 <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a> <a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1> 2559 <h2 id="rfc.section.D.1"><a href="#rfc.section.D.1">D.1</a> Since RFC2616 2565 2560 </h2> 2566 <p id="rfc.section. E.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.2567 </p> 2568 <h2 id="rfc.section. E.2"><a href="#rfc.section.E.2">E.2</a> Since draft-ietf-httpbis-p1-messaging-002561 <p id="rfc.section.D.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>. 2562 </p> 2563 <h2 id="rfc.section.D.2"><a href="#rfc.section.D.2">D.2</a> Since draft-ietf-httpbis-p1-messaging-00 2569 2564 </h2> 2570 <p id="rfc.section. E.2.p.1">Closed issues: </p>2565 <p id="rfc.section.D.2.p.1">Closed issues: </p> 2571 2566 <ul> 2572 2567 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/1">http://tools.ietf.org/wg/httpbis/trac/ticket/1</a>>: "HTTP Version should be case sensitive" (<<a href="http://purl.org/NET/http-errata#verscase">http://purl.org/NET/http-errata#verscase</a>>) … … 2609 2604 </li> 2610 2605 </ul> 2611 <p id="rfc.section. E.2.p.2">Other changes: </p>2606 <p id="rfc.section.D.2.p.2">Other changes: </p> 2612 2607 <ul> 2613 2608 <li>Update media type registrations to use RFC4288 template.</li> … … 2615 2610 </li> 2616 2611 </ul> 2617 <h2 id="rfc.section. E.3"><a href="#rfc.section.E.3">E.3</a> Since draft-ietf-httpbis-p1-messaging-012612 <h2 id="rfc.section.D.3"><a href="#rfc.section.D.3">D.3</a> Since draft-ietf-httpbis-p1-messaging-01 2618 2613 </h2> 2619 <p id="rfc.section. E.3.p.1">Closed issues: </p>2614 <p id="rfc.section.D.3.p.1">Closed issues: </p> 2620 2615 <ul> 2621 2616 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/19">http://tools.ietf.org/wg/httpbis/trac/ticket/19</a>>: "Bodies on GET (and other) requests" … … 2628 2623 </li> 2629 2624 </ul> 2630 <p id="rfc.section. E.3.p.2">Ongoing work on ABNF conversion (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>):2625 <p id="rfc.section.D.3.p.2">Ongoing work on ABNF conversion (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>): 2631 2626 </p> 2632 2627 <ul> … … 2643 2638 <li>Rewrite prose rule "token" in terms of "tchar", rewrite prose rule "TEXT".</li> 2644 2639 </ul> 2645 <h2 id="rfc.section. E.4"><a href="#rfc.section.E.4">E.4</a> <a id="changes.since.02" href="#changes.since.02">Since draft-ietf-httpbis-p1-messaging-02</a></h2>2646 <p id="rfc.section. E.4.p.1">Closed issues: </p>2640 <h2 id="rfc.section.D.4"><a href="#rfc.section.D.4">D.4</a> <a id="changes.since.02" href="#changes.since.02">Since draft-ietf-httpbis-p1-messaging-02</a></h2> 2641 <p id="rfc.section.D.4.p.1">Closed issues: </p> 2647 2642 <ul> 2648 2643 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/51">http://tools.ietf.org/wg/httpbis/trac/ticket/51</a>>: "HTTP-date vs. rfc1123-date" … … 2651 2646 </li> 2652 2647 </ul> 2653 <p id="rfc.section. E.4.p.2">Ongoing work on IANA Message Header Registration (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>>):2648 <p id="rfc.section.D.4.p.2">Ongoing work on IANA Message Header Registration (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>>): 2654 2649 </p> 2655 2650 <ul> 2656 2651 <li>Reference RFC 3984, and update header registrations for headers defined in this document.</li> 2657 2652 </ul> 2658 <p id="rfc.section. E.4.p.3">Ongoing work on ABNF conversion (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>):2653 <p id="rfc.section.D.4.p.3">Ongoing work on ABNF conversion (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>): 2659 2654 </p> 2660 2655 <ul> 2661 2656 <li>Replace string literals when the string really is case-sensitive (HTTP-Version).</li> 2662 2657 </ul> 2663 <h2 id="rfc.section. E.5"><a href="#rfc.section.E.5">E.5</a> <a id="changes.since.03" href="#changes.since.03">Since draft-ietf-httpbis-p1-messaging-03</a></h2>2664 <p id="rfc.section. E.5.p.1">Closed issues: </p>2658 <h2 id="rfc.section.D.5"><a href="#rfc.section.D.5">D.5</a> <a id="changes.since.03" href="#changes.since.03">Since draft-ietf-httpbis-p1-messaging-03</a></h2> 2659 <p id="rfc.section.D.5.p.1">Closed issues: </p> 2665 2660 <ul> 2666 2661 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/28">http://tools.ietf.org/wg/httpbis/trac/ticket/28</a>>: "Connection closing" … … 2677 2672 </li> 2678 2673 </ul> 2679 <p id="rfc.section. E.5.p.2">Ongoing work on ABNF conversion (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>):2674 <p id="rfc.section.D.5.p.2">Ongoing work on ABNF conversion (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>): 2680 2675 </p> 2681 2676 <ul> … … 2683 2678 <li>Replace HEX by HEXDIG for future consistence with RFC 5234's core rules.</li> 2684 2679 </ul> 2685 <h2 id="rfc.section. E.6"><a href="#rfc.section.E.6">E.6</a> <a id="changes.since.04" href="#changes.since.04">Since draft-ietf-httpbis-p1-messaging-04</a></h2>2686 <p id="rfc.section. E.6.p.1">Closed issues: </p>2680 <h2 id="rfc.section.D.6"><a href="#rfc.section.D.6">D.6</a> <a id="changes.since.04" href="#changes.since.04">Since draft-ietf-httpbis-p1-messaging-04</a></h2> 2681 <p id="rfc.section.D.6.p.1">Closed issues: </p> 2687 2682 <ul> 2688 2683 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/34">http://tools.ietf.org/wg/httpbis/trac/ticket/34</a>>: "Out-of-date reference for URIs" … … 2691 2686 </li> 2692 2687 </ul> 2693 <p id="rfc.section. E.6.p.2">Ongoing work on ABNF conversion (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>):2688 <p id="rfc.section.D.6.p.2">Ongoing work on ABNF conversion (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>): 2694 2689 </p> 2695 2690 <ul> … … 2700 2695 <li>Rewrite ABNFs to spell out whitespace rules, factor out header value format definitions.</li> 2701 2696 </ul> 2702 <h2 id="rfc.section. E.7"><a href="#rfc.section.E.7">E.7</a> <a id="changes.since.05" href="#changes.since.05">Since draft-ietf-httpbis-p1-messaging-05</a></h2>2703 <p id="rfc.section. E.7.p.1">Closed issues: </p>2697 <h2 id="rfc.section.D.7"><a href="#rfc.section.D.7">D.7</a> <a id="changes.since.05" href="#changes.since.05">Since draft-ietf-httpbis-p1-messaging-05</a></h2> 2698 <p id="rfc.section.D.7.p.1">Closed issues: </p> 2704 2699 <ul> 2700 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/118">http://tools.ietf.org/wg/httpbis/trac/ticket/118</a>>: "Join "Differences Between HTTP Entities and RFC 2045 Entities"?" 2701 </li> 2705 2702 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/134">http://tools.ietf.org/wg/httpbis/trac/ticket/134</a>>: "RFC822 reference left in discussion of date formats" 2706 2703 </li> … … 2740 2737 </li> 2741 2738 <li class="indline0"><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul class="ind"> 2742 <li class="indline1">cache <a class="iref" href="#rfc.iref.c.6"> D</a></li>2743 <li class="indline1">cacheable <a class="iref" href="#rfc.iref.c.7"> D</a></li>2744 <li class="indline1">client <a class="iref" href="#rfc.iref.c.5"> D</a></li>2745 <li class="indline1">connection <a class="iref" href="#rfc.iref.c.3"> D</a></li>2746 <li class="indline1">Connection header <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.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>2747 <li class="indline1">content negotiation <a class="iref" href="#rfc.iref.c.4"> D</a></li>2748 <li class="indline1">Content-Length header <a class="iref" href="#rfc.xref.header.content-length.1">4.4</a>, <a class="iref" href="#rfc.iref.c.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>2739 <li class="indline1">cache <a class="iref" href="#rfc.iref.c.6">C</a></li> 2740 <li class="indline1">cacheable <a class="iref" href="#rfc.iref.c.7">C</a></li> 2741 <li class="indline1">client <a class="iref" href="#rfc.iref.c.5">C</a></li> 2742 <li class="indline1">connection <a class="iref" href="#rfc.iref.c.3">C</a></li> 2743 <li class="indline1">Connection header <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.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">B.2</a>, <a class="iref" href="#rfc.xref.header.connection.8">B.4</a></li> 2744 <li class="indline1">content negotiation <a class="iref" href="#rfc.iref.c.4">C</a></li> 2745 <li class="indline1">Content-Length header <a class="iref" href="#rfc.xref.header.content-length.1">4.4</a>, <a class="iref" href="#rfc.iref.c.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">B.3</a></li> 2749 2746 </ul> 2750 2747 </li> 2751 2748 <li class="indline0"><a id="rfc.index.D" href="#rfc.index.D"><b>D</b></a><ul class="ind"> 2752 2749 <li class="indline1">Date header <a class="iref" href="#rfc.xref.header.date.1">4.5</a>, <a class="iref" href="#rfc.iref.d.1"><b>8.3</b></a>, <a class="iref" href="#rfc.xref.header.date.2">9.1</a></li> 2753 <li class="indline1">downstream <a class="iref" href="#rfc.iref.d.2"> D</a></li>2750 <li class="indline1">downstream <a class="iref" href="#rfc.iref.d.2">C</a></li> 2754 2751 </ul> 2755 2752 </li> 2756 2753 <li class="indline0"><a id="rfc.index.E" href="#rfc.index.E"><b>E</b></a><ul class="ind"> 2757 <li class="indline1">entity <a class="iref" href="#rfc.iref.e.1"> D</a></li>2754 <li class="indline1">entity <a class="iref" href="#rfc.iref.e.1">C</a></li> 2758 2755 </ul> 2759 2756 </li> 2760 2757 <li class="indline0"><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul class="ind"> 2761 <li class="indline1">gateway <a class="iref" href="#rfc.iref.g.97"> D</a></li>2758 <li class="indline1">gateway <a class="iref" href="#rfc.iref.g.97">C</a></li> 2762 2759 <li class="indline1"><tt>Grammar</tt> 2763 2760 <ul class="ind"> … … 2865 2862 <li class="indline1">Headers 2866 2863 <ul class="ind"> 2867 <li class="indline1">Connection <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.3"><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>2868 <li class="indline1">Content-Length <a class="iref" href="#rfc.xref.header.content-length.1">4.4</a>, <a class="iref" href="#rfc.iref.h.4"><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>2864 <li class="indline1">Connection <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.3"><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">B.2</a>, <a class="iref" href="#rfc.xref.header.connection.8">B.4</a></li> 2865 <li class="indline1">Content-Length <a class="iref" href="#rfc.xref.header.content-length.1">4.4</a>, <a class="iref" href="#rfc.iref.h.4"><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">B.3</a></li> 2869 2866 <li class="indline1">Date <a class="iref" href="#rfc.xref.header.date.1">4.5</a>, <a class="iref" href="#rfc.iref.h.5"><b>8.3</b></a>, <a class="iref" href="#rfc.xref.header.date.2">9.1</a></li> 2870 <li class="indline1">Host <a class="iref" href="#rfc.iref.h.7"><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>2871 <li class="indline1">TE <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.8"><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>2867 <li class="indline1">Host <a class="iref" href="#rfc.iref.h.7"><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">B.1.1</a></li> 2868 <li class="indline1">TE <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.8"><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">B.3</a></li> 2872 2869 <li class="indline1">Trailer <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.9"><b>8.6</b></a>, <a class="iref" href="#rfc.xref.header.trailer.3">9.1</a></li> 2873 2870 <li class="indline1">Transfer-Encoding <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.10"><b>8.7</b></a>, <a class="iref" href="#rfc.xref.header.transfer-encoding.5">9.1</a></li> … … 2876 2873 </ul> 2877 2874 </li> 2878 <li class="indline1">Host header <a class="iref" href="#rfc.iref.h.6"><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>2875 <li class="indline1">Host header <a class="iref" href="#rfc.iref.h.6"><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">B.1.1</a></li> 2879 2876 <li class="indline1">http URI scheme <a class="iref" href="#rfc.iref.h.1"><b>3.2.1</b></a></li> 2880 2877 <li class="indline1">https URI scheme <a class="iref" href="#rfc.iref.h.2">3.2.1</a></li> … … 2882 2879 </li> 2883 2880 <li class="indline0"><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul class="ind"> 2884 <li class="indline1">inbound <a class="iref" href="#rfc.iref.i.1"> D</a></li>2881 <li class="indline1">inbound <a class="iref" href="#rfc.iref.i.1">C</a></li> 2885 2882 <li class="indline1"><em>ISO-8859-1</em> <a class="iref" href="#rfc.xref.ISO-8859-1.1">2.2</a>, <a class="iref" href="#ISO-8859-1"><b>12.1</b></a></li> 2886 2883 </ul> … … 2897 2894 </ul> 2898 2895 </li> 2899 <li class="indline1">message <a class="iref" href="#rfc.iref.m.4"> D</a></li>2896 <li class="indline1">message <a class="iref" href="#rfc.iref.m.4">C</a></li> 2900 2897 <li class="indline1">message/http Media Type <a class="iref" href="#rfc.iref.m.2"><b>9.3.1</b></a></li> 2901 2898 </ul> 2902 2899 </li> 2903 2900 <li class="indline0"><a id="rfc.index.N" href="#rfc.index.N"><b>N</b></a><ul class="ind"> 2904 <li class="indline1"><em>Nie1997</em> <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>2901 <li class="indline1"><em>Nie1997</em> <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">B.3</a></li> 2905 2902 </ul> 2906 2903 </li> 2907 2904 <li class="indline0"><a id="rfc.index.O" href="#rfc.index.O"><b>O</b></a><ul class="ind"> 2908 <li class="indline1">origin server <a class="iref" href="#rfc.iref.o.1"> D</a></li>2909 <li class="indline1">outbound <a class="iref" href="#rfc.iref.o.2"> D</a></li>2905 <li class="indline1">origin server <a class="iref" href="#rfc.iref.o.1">C</a></li> 2906 <li class="indline1">outbound <a class="iref" href="#rfc.iref.o.2">C</a></li> 2910 2907 </ul> 2911 2908 </li> … … 2925 2922 </ul> 2926 2923 </li> 2927 <li class="indline1"><em>Part3</em> <a class="iref" href="#rfc.xref.Part3.1">1</a>, <a class="iref" href="#rfc.xref.Part3.2">1.2</a>, <a class="iref" href="#rfc.xref.Part3.3">2.2</a>, <a class="iref" href="#rfc.xref.Part3.4">2.3</a>, <a class="iref" href="#rfc.xref.Part3.5">2.3</a>, <a class="iref" href="#rfc.xref.Part3.6">2.3</a>, <a class="iref" href="#rfc.xref.Part3.7">3.4</a>, <a class="iref" href="#rfc.xref.Part3.8">3.4</a>, <a class="iref" href="#rfc.xref.Part3.9">4.2</a>, <a class="iref" href="#rfc.xref.Part3.10">5</a>, <a class="iref" href="#rfc.xref.Part3.11">6</a>, <a class="iref" href="#rfc.xref.Part3.12">8.5</a>, <a class="iref" href="#Part3"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.Part3.13">A</a>, <a class="iref" href="#rfc.xref.Part3.14"> C.3</a>, <a class="iref" href="#rfc.xref.Part3.15">D</a>, <a class="iref" href="#rfc.xref.Part3.16">D</a>, <a class="iref" href="#rfc.xref.Part3.17">D</a><ul class="ind">2924 <li class="indline1"><em>Part3</em> <a class="iref" href="#rfc.xref.Part3.1">1</a>, <a class="iref" href="#rfc.xref.Part3.2">1.2</a>, <a class="iref" href="#rfc.xref.Part3.3">2.2</a>, <a class="iref" href="#rfc.xref.Part3.4">2.3</a>, <a class="iref" href="#rfc.xref.Part3.5">2.3</a>, <a class="iref" href="#rfc.xref.Part3.6">2.3</a>, <a class="iref" href="#rfc.xref.Part3.7">3.4</a>, <a class="iref" href="#rfc.xref.Part3.8">3.4</a>, <a class="iref" href="#rfc.xref.Part3.9">4.2</a>, <a class="iref" href="#rfc.xref.Part3.10">5</a>, <a class="iref" href="#rfc.xref.Part3.11">6</a>, <a class="iref" href="#rfc.xref.Part3.12">8.5</a>, <a class="iref" href="#Part3"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.Part3.13">A</a>, <a class="iref" href="#rfc.xref.Part3.14">B.3</a>, <a class="iref" href="#rfc.xref.Part3.15">C</a>, <a class="iref" href="#rfc.xref.Part3.16">C</a>, <a class="iref" href="#rfc.xref.Part3.17">C</a><ul class="ind"> 2928 2925 <li class="indline1"><em>Section 3.2</em> <a class="iref" href="#rfc.xref.Part3.7">3.4</a>, <a class="iref" href="#rfc.xref.Part3.8">3.4</a></li> 2929 2926 <li class="indline1"><em>Section 3.3</em> <a class="iref" href="#rfc.xref.Part3.3">2.2</a></li> 2930 2927 <li class="indline1"><em>Section 3.4</em> <a class="iref" href="#rfc.xref.Part3.12">8.5</a></li> 2931 2928 <li class="indline1"><em>Section 4.1</em> <a class="iref" href="#rfc.xref.Part3.6">2.3</a>, <a class="iref" href="#rfc.xref.Part3.9">4.2</a>, <a class="iref" href="#rfc.xref.Part3.10">5</a>, <a class="iref" href="#rfc.xref.Part3.11">6</a></li> 2932 <li class="indline1"><em>Section 4</em> <a class="iref" href="#rfc.xref.Part3.15"> D</a></li>2929 <li class="indline1"><em>Section 4</em> <a class="iref" href="#rfc.xref.Part3.15">C</a></li> 2933 2930 <li class="indline1"><em>Section 4.2</em> <a class="iref" href="#rfc.xref.Part3.5">2.3</a></li> 2934 <li class="indline1"><em>Section 5</em> <a class="iref" href="#rfc.xref.Part3.16"> D</a>, <a class="iref" href="#rfc.xref.Part3.17">D</a></li>2931 <li class="indline1"><em>Section 5</em> <a class="iref" href="#rfc.xref.Part3.16">C</a>, <a class="iref" href="#rfc.xref.Part3.17">C</a></li> 2935 2932 <li class="indline1"><em>Section 6.1</em> <a class="iref" href="#rfc.xref.Part3.4">2.3</a></li> 2936 2933 <li class="indline1"><em>Appendix A</em> <a class="iref" href="#rfc.xref.Part3.1">1</a>, <a class="iref" href="#rfc.xref.Part3.2">1.2</a></li> 2937 2934 </ul> 2938 2935 </li> 2939 <li class="indline1"><em>Part5</em> <a class="iref" href="#Part5"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.Part5.1"> C.3</a></li>2940 <li class="indline1"><em>Part6</em> <a class="iref" href="#rfc.xref.Part6.1">1.2</a>, <a class="iref" href="#rfc.xref.Part6.2">2.3</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">4.5</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="#Part6"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.Part6.8"> C.3</a>, <a class="iref" href="#rfc.xref.Part6.9">D</a><ul class="ind">2941 <li class="indline1"><em>Section 1</em> <a class="iref" href="#rfc.xref.Part6.1">1.2</a>, <a class="iref" href="#rfc.xref.Part6.9"> D</a></li>2936 <li class="indline1"><em>Part5</em> <a class="iref" href="#Part5"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.Part5.1">B.3</a></li> 2937 <li class="indline1"><em>Part6</em> <a class="iref" href="#rfc.xref.Part6.1">1.2</a>, <a class="iref" href="#rfc.xref.Part6.2">2.3</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">4.5</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="#Part6"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.Part6.8">B.3</a>, <a class="iref" href="#rfc.xref.Part6.9">C</a><ul class="ind"> 2938 <li class="indline1"><em>Section 1</em> <a class="iref" href="#rfc.xref.Part6.1">1.2</a>, <a class="iref" href="#rfc.xref.Part6.9">C</a></li> 2942 2939 <li class="indline1"><em>Section 16.2</em> <a class="iref" href="#rfc.xref.Part6.5">4.5</a></li> 2943 2940 <li class="indline1"><em>Section 16.4</em> <a class="iref" href="#rfc.xref.Part6.2">2.3</a>, <a class="iref" href="#rfc.xref.Part6.3">2.3</a>, <a class="iref" href="#rfc.xref.Part6.6">4.5</a></li> … … 2945 2942 </ul> 2946 2943 </li> 2947 <li class="indline1">proxy <a class="iref" href="#rfc.iref.p.1"> D</a></li>2944 <li class="indline1">proxy <a class="iref" href="#rfc.iref.p.1">C</a></li> 2948 2945 </ul> 2949 2946 </li> 2950 2947 <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind"> 2951 <li class="indline1">representation <a class="iref" href="#rfc.iref.r.4"> D</a></li>2952 <li class="indline1">request <a class="iref" href="#rfc.iref.r.1"> D</a></li>2953 <li class="indline1">resource <a class="iref" href="#rfc.iref.r.3"> D</a></li>2954 <li class="indline1">response <a class="iref" href="#rfc.iref.r.2"> D</a></li>2948 <li class="indline1">representation <a class="iref" href="#rfc.iref.r.4">C</a></li> 2949 <li class="indline1">request <a class="iref" href="#rfc.iref.r.1">C</a></li> 2950 <li class="indline1">resource <a class="iref" href="#rfc.iref.r.3">C</a></li> 2951 <li class="indline1">response <a class="iref" href="#rfc.iref.r.2">C</a></li> 2955 2952 <li class="indline1"><em>RFC1123</em> <a class="iref" href="#rfc.xref.RFC1123.1">3.3.1</a>, <a class="iref" href="#RFC1123"><b>12.2</b></a></li> 2956 2953 <li class="indline1"><em>RFC1305</em> <a class="iref" href="#rfc.xref.RFC1305.1">8.3</a>, <a class="iref" href="#RFC1305"><b>12.2</b></a></li> 2957 2954 <li class="indline1"><em>RFC1436</em> <a class="iref" href="#rfc.xref.RFC1436.1">1</a>, <a class="iref" href="#RFC1436"><b>12.2</b></a></li> 2958 2955 <li class="indline1"><em>RFC1900</em> <a class="iref" href="#rfc.xref.RFC1900.1">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC1900.2">10.4</a>, <a class="iref" href="#RFC1900"><b>12.2</b></a></li> 2959 <li class="indline1"><em>RFC1945</em> <a class="iref" href="#RFC1945"><b>12.2</b></a>, <a class="iref" href="#rfc.xref.RFC1945.1"> C</a></li>2956 <li class="indline1"><em>RFC1945</em> <a class="iref" href="#RFC1945"><b>12.2</b></a>, <a class="iref" href="#rfc.xref.RFC1945.1">B</a></li> 2960 2957 <li class="indline1"><em>RFC2045</em> <a class="iref" href="#rfc.xref.RFC2045.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> 2961 2958 <li class="indline1"><em>RFC2047</em> <a class="iref" href="#rfc.xref.RFC2047.1">2.2</a>, <a class="iref" href="#RFC2047"><b>12.1</b></a></li> 2962 <li class="indline1"><em>RFC2068</em> <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">2963 <li class="indline1"><em>Section 19.7.1</em> <a class="iref" href="#rfc.xref.RFC2068.6"> C</a></li>2959 <li class="indline1"><em>RFC2068</em> <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">B</a>, <a class="iref" href="#rfc.xref.RFC2068.7">B.2</a><ul class="ind"> 2960 <li class="indline1"><em>Section 19.7.1</em> <a class="iref" href="#rfc.xref.RFC2068.6">B</a></li> 2964 2961 </ul> 2965 2962 </li> 2966 2963 <li class="indline1"><em>RFC2109</em> <a class="iref" href="#rfc.xref.RFC2109.1">4.2</a>, <a class="iref" href="#RFC2109"><b>12.2</b></a></li> 2967 <li class="indline1"><em>RFC2119</em> <a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.RFC2119.2"> C.3</a></li>2968 <li class="indline1"><em>RFC2145</em> <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>2969 <li class="indline1"><em>RFC2616</em> <a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#rfc.xref.RFC2616.2">11</a>, <a class="iref" href="#RFC2616"><b>12.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.3"> E.1</a></li>2964 <li class="indline1"><em>RFC2119</em> <a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.RFC2119.2">B.3</a></li> 2965 <li class="indline1"><em>RFC2145</em> <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">B.3</a></li> 2966 <li class="indline1"><em>RFC2616</em> <a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#rfc.xref.RFC2616.2">11</a>, <a class="iref" href="#RFC2616"><b>12.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.3">D.1</a></li> 2970 2967 <li class="indline1"><em>RFC2818</em> <a class="iref" href="#rfc.xref.RFC2818.1">3.2.1</a>, <a class="iref" href="#RFC2818"><b>12.2</b></a></li> 2971 2968 <li class="indline1"><em>RFC2965</em> <a class="iref" href="#rfc.xref.RFC2965.1">4.2</a>, <a class="iref" href="#RFC2965"><b>12.2</b></a></li> … … 3001 2998 </li> 3002 2999 <li class="indline0"><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul class="ind"> 3003 <li class="indline1">server <a class="iref" href="#rfc.iref.s.1"> D</a></li>3000 <li class="indline1">server <a class="iref" href="#rfc.iref.s.1">C</a></li> 3004 3001 <li class="indline1"><em>Spe</em> <a class="iref" href="#rfc.xref.Spe.1">7.1.1</a>, <a class="iref" href="#Spe"><b>12.2</b></a></li> 3005 3002 </ul> 3006 3003 </li> 3007 3004 <li class="indline0"><a id="rfc.index.T" href="#rfc.index.T"><b>T</b></a><ul class="ind"> 3008 <li class="indline1">TE header <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.1"><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>3005 <li class="indline1">TE header <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.1"><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">B.3</a></li> 3009 3006 <li class="indline1"><em>Tou1998</em> <a class="iref" href="#rfc.xref.Tou1998.1">7.1.1</a>, <a class="iref" href="#Tou1998"><b>12.2</b></a></li> 3010 3007 <li class="indline1">Trailer header <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.2"><b>8.6</b></a>, <a class="iref" href="#rfc.xref.header.trailer.3">9.1</a></li> 3011 3008 <li class="indline1">Transfer-Encoding header <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.t.3"><b>8.7</b></a>, <a class="iref" href="#rfc.xref.header.transfer-encoding.5">9.1</a></li> 3012 <li class="indline1">tunnel <a class="iref" href="#rfc.iref.t.4"> D</a></li>3009 <li class="indline1">tunnel <a class="iref" href="#rfc.iref.t.4">C</a></li> 3013 3010 </ul> 3014 3011 </li> 3015 3012 <li class="indline0"><a id="rfc.index.U" href="#rfc.index.U"><b>U</b></a><ul class="ind"> 3016 3013 <li class="indline1">Upgrade header <a class="iref" href="#rfc.xref.header.upgrade.1">4.5</a>, <a class="iref" href="#rfc.iref.u.3"><b>8.8</b></a>, <a class="iref" href="#rfc.xref.header.upgrade.2">9.1</a></li> 3017 <li class="indline1">upstream <a class="iref" href="#rfc.iref.u.5"> D</a></li>3014 <li class="indline1">upstream <a class="iref" href="#rfc.iref.u.5">C</a></li> 3018 3015 <li class="indline1">URI scheme 3019 3016 <ul class="ind"> … … 3023 3020 </li> 3024 3021 <li class="indline1"><em>USASCII</em> <a class="iref" href="#rfc.xref.USASCII.1">2.2</a>, <a class="iref" href="#USASCII"><b>12.1</b></a></li> 3025 <li class="indline1">user agent <a class="iref" href="#rfc.iref.u.4"> D</a></li>3022 <li class="indline1">user agent <a class="iref" href="#rfc.iref.u.4">C</a></li> 3026 3023 </ul> 3027 3024 </li> 3028 3025 <li class="indline0"><a id="rfc.index.V" href="#rfc.index.V"><b>V</b></a><ul class="ind"> 3029 <li class="indline1">variant <a class="iref" href="#rfc.iref.v.2"> D</a></li>3026 <li class="indline1">variant <a class="iref" href="#rfc.iref.v.2">C</a></li> 3030 3027 <li class="indline1">Via header <a class="iref" href="#rfc.xref.header.via.1">4.5</a>, <a class="iref" href="#rfc.iref.v.1"><b>8.9</b></a>, <a class="iref" href="#rfc.xref.header.via.2">9.1</a></li> 3031 3028 </ul> -
draft-ietf-httpbis/latest/p1-messaging.xml
r384 r385 3828 3828 </section> 3829 3829 3830 <section title="Conversion of Date Formats" anchor="conversion.of.date.formats">3831 <t>3832 HTTP/1.1 uses a restricted set of date formats (<xref target="full.date"/>) to3833 simplify the process of date comparison. Proxies and gateways from3834 other protocols &SHOULD; ensure that any Date header field present in a3835 message conforms to one of the HTTP/1.1 formats and rewrite the date3836 if necessary.3837 </t>3838 </section>3839 3840 3830 <section title="Compatibility with Previous Versions" anchor="compatibility"> 3841 3831 <t> … … 4585 4575 <list style="symbols"> 4586 4576 <t> 4577 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/118"/>: 4578 "Join "Differences Between HTTP Entities and RFC 2045 Entities"?" 4579 </t> 4580 <t> 4587 4581 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/134"/>: 4588 4582 "RFC822 reference left in discussion of date formats" -
draft-ietf-httpbis/latest/p3-payload.html
r382 r385 586 586 <li class="tocline1">A.1 <a href="#mime-version">MIME-Version</a></li> 587 587 <li class="tocline1">A.2 <a href="#conversion.to.canonical.form">Conversion to Canonical Form</a></li> 588 <li class="tocline1">A.3 <a href="#introduction.of.content-encoding">Introduction of Content-Encoding</a></li> 589 <li class="tocline1">A.4 <a href="#no.content-transfer-encoding">No Content-Transfer-Encoding</a></li> 590 <li class="tocline1">A.5 <a href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></li> 591 <li class="tocline1">A.6 <a href="#mhtml.line.length">MHTML and Line Length Limitations</a></li> 588 <li class="tocline1">A.3 <a href="#conversion.of.date.formats">Conversion of Date Formats</a></li> 589 <li class="tocline1">A.4 <a href="#introduction.of.content-encoding">Introduction of Content-Encoding</a></li> 590 <li class="tocline1">A.5 <a href="#no.content-transfer-encoding">No Content-Transfer-Encoding</a></li> 591 <li class="tocline1">A.6 <a href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></li> 592 <li class="tocline1">A.7 <a href="#mhtml.line.length">MHTML and Line Length Limitations</a></li> 592 593 </ul> 593 594 </li> … … 1607 1608 checksums in HTTP. 1608 1609 </p> 1609 <h2 id="rfc.section.A.3"><a href="#rfc.section.A.3">A.3</a> <a id="introduction.of.content-encoding" href="#introduction.of.content-encoding">Introduction of Content-Encoding</a></h2> 1610 <p id="rfc.section.A.3.p.1">RFC 2045 does not include any concept equivalent to HTTP/1.1's Content-Encoding header field. Since this acts as a modifier 1610 <h2 id="rfc.section.A.3"><a href="#rfc.section.A.3">A.3</a> <a id="conversion.of.date.formats" href="#conversion.of.date.formats">Conversion of Date Formats</a></h2> 1611 <p id="rfc.section.A.3.p.1">HTTP/1.1 uses a restricted set of date formats (<a href="p1-messaging.html#full.date" title="Full Date">Section 3.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></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. 1612 </p> 1613 <h2 id="rfc.section.A.4"><a href="#rfc.section.A.4">A.4</a> <a id="introduction.of.content-encoding" href="#introduction.of.content-encoding">Introduction of Content-Encoding</a></h2> 1614 <p id="rfc.section.A.4.p.1">RFC 2045 does not include any concept equivalent to HTTP/1.1's Content-Encoding header field. Since this acts as a modifier 1611 1615 on the media type, proxies and gateways from HTTP to MIME-compliant protocols <em class="bcp14">MUST</em> either change the value of the Content-Type header field or decode the entity-body before forwarding the message. (Some experimental 1612 1616 applications of Content-Type for Internet mail have used a media-type parameter of ";conversions=<content-coding>" to perform 1613 1617 a function equivalent to Content-Encoding. However, this parameter is not part of RFC 2045). 1614 1618 </p> 1615 <h2 id="rfc.section.A. 4"><a href="#rfc.section.A.4">A.4</a> <a id="no.content-transfer-encoding" href="#no.content-transfer-encoding">No Content-Transfer-Encoding</a></h2>1616 <p id="rfc.section.A. 4.p.1">HTTP does not use the Content-Transfer-Encoding field of RFC 2045. Proxies and gateways from MIME-compliant protocols to HTTP <em class="bcp14">MUST</em> remove any Content-Transfer-Encoding prior to delivering the response message to an HTTP client.1617 </p> 1618 <p id="rfc.section.A. 4.p.2">Proxies and gateways from HTTP to MIME-compliant protocols are responsible for ensuring that the message is in the correct1619 <h2 id="rfc.section.A.5"><a href="#rfc.section.A.5">A.5</a> <a id="no.content-transfer-encoding" href="#no.content-transfer-encoding">No Content-Transfer-Encoding</a></h2> 1620 <p id="rfc.section.A.5.p.1">HTTP does not use the Content-Transfer-Encoding field of RFC 2045. Proxies and gateways from MIME-compliant protocols to HTTP <em class="bcp14">MUST</em> remove any Content-Transfer-Encoding prior to delivering the response message to an HTTP client. 1621 </p> 1622 <p id="rfc.section.A.5.p.2">Proxies and gateways from HTTP to MIME-compliant protocols are responsible for ensuring that the message is in the correct 1619 1623 format and encoding for safe transport on that protocol, where "safe transport" is defined by the limitations of the protocol 1620 1624 being used. Such a proxy or gateway <em class="bcp14">SHOULD</em> label the data with an appropriate Content-Transfer-Encoding if doing so will improve the likelihood of safe transport over 1621 1625 the destination protocol. 1622 1626 </p> 1623 <h2 id="rfc.section.A. 5"><a href="#rfc.section.A.5">A.5</a> <a id="introduction.of.transfer-encoding" href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></h2>1624 <p id="rfc.section.A. 5.p.1">HTTP/1.1 introduces the Transfer-Encoding header field (<a href="p1-messaging.html#header.transfer-encoding" title="Transfer-Encoding">Section 8.7</a> of <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). Proxies/gateways <em class="bcp14">MUST</em> remove any transfer-coding prior to forwarding a message via a MIME-compliant protocol.1625 </p> 1626 <h2 id="rfc.section.A. 6"><a href="#rfc.section.A.6">A.6</a> <a id="mhtml.line.length" href="#mhtml.line.length">MHTML and Line Length Limitations</a></h2>1627 <p id="rfc.section.A. 6.p.1">HTTP implementations which share code with MHTML <a href="#RFC2557" id="rfc.xref.RFC2557.1"><cite title="MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)">[RFC2557]</cite></a> implementations need to be aware of MIME line length limitations. Since HTTP does not have this limitation, HTTP does not1627 <h2 id="rfc.section.A.6"><a href="#rfc.section.A.6">A.6</a> <a id="introduction.of.transfer-encoding" href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></h2> 1628 <p id="rfc.section.A.6.p.1">HTTP/1.1 introduces the Transfer-Encoding header field (<a href="p1-messaging.html#header.transfer-encoding" title="Transfer-Encoding">Section 8.7</a> of <a href="#Part1" id="rfc.xref.Part1.17"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). Proxies/gateways <em class="bcp14">MUST</em> remove any transfer-coding prior to forwarding a message via a MIME-compliant protocol. 1629 </p> 1630 <h2 id="rfc.section.A.7"><a href="#rfc.section.A.7">A.7</a> <a id="mhtml.line.length" href="#mhtml.line.length">MHTML and Line Length Limitations</a></h2> 1631 <p id="rfc.section.A.7.p.1">HTTP implementations which share code with MHTML <a href="#RFC2557" id="rfc.xref.RFC2557.1"><cite title="MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)">[RFC2557]</cite></a> implementations need to be aware of MIME line length limitations. Since HTTP does not have this limitation, HTTP does not 1628 1632 fold long lines. MHTML messages being transported by HTTP follow all conventions of MHTML, including line length limitations 1629 1633 and folding, canonicalization, etc., since HTTP transports all message-bodies as payload (see <a href="#multipart.types" title="Multipart Types">Section 3.3.2</a>) and does not interpret the content or any MIME header lines that might be contained therein. … … 1667 1671 <p id="rfc.section.C.1.p.1">Transfer-coding and message lengths all interact in ways that required fixing exactly when chunked encoding is used (to allow 1668 1672 for transfer encoding that may not be self delimiting); it was important to straighten out exactly how message lengths are 1669 computed. (<a href="#entity.length" title="Entity Length">Section 4.2.2</a>, see also <a href="#Part1" id="rfc.xref.Part1.1 7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="#Part5" id="rfc.xref.Part5.4"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a> and <a href="#Part6" id="rfc.xref.Part6.5"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).1673 computed. (<a href="#entity.length" title="Entity Length">Section 4.2.2</a>, see also <a href="#Part1" id="rfc.xref.Part1.18"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="#Part5" id="rfc.xref.Part5.4"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a> and <a href="#Part6" id="rfc.xref.Part6.5"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>). 1670 1674 </p> 1671 1675 <p id="rfc.section.C.1.p.2">Charset wildcarding is introduced to avoid explosion of character set names in accept headers. (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset.3" title="Accept-Charset">Section 6.2</a>) … … 1683 1687 <p id="rfc.section.C.2.p.1">Clarify contexts that charset is used in. (<a href="#character.sets" title="Character Sets">Section 3.1</a>) 1684 1688 </p> 1685 <p id="rfc.section.C.2.p.2">Remove reference to non-existant identity transfer-coding value tokens. (<a href="#no.content-transfer-encoding" title="No Content-Transfer-Encoding">Appendix A. 4</a>)1689 <p id="rfc.section.C.2.p.2">Remove reference to non-existant identity transfer-coding value tokens. (<a href="#no.content-transfer-encoding" title="No Content-Transfer-Encoding">Appendix A.5</a>) 1686 1690 </p> 1687 1691 <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a> <a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1> … … 1768 1772 </ul> 1769 1773 <h2 id="rfc.section.D.7"><a href="#rfc.section.D.7">D.7</a> <a id="changes.since.05" href="#changes.since.05">Since draft-ietf-httpbis-p3-payload-05</a></h2> 1774 <p id="rfc.section.D.7.p.1">Closed issues: </p> 1775 <ul> 1776 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/118">http://tools.ietf.org/wg/httpbis/trac/ticket/118</a>>: "Join "Differences Between HTTP Entities and RFC 2045 Entities"?" 1777 </li> 1778 </ul> 1770 1779 <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1> 1771 1780 <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the … … 1920 1929 </li> 1921 1930 <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind"> 1922 <li class="indline1"><em>Part1</em> <a class="iref" href="#rfc.xref.Part1.1">2</a>, <a class="iref" href="#rfc.xref.Part1.2">2</a>, <a class="iref" href="#rfc.xref.Part1.3">2</a>, <a class="iref" href="#rfc.xref.Part1.4">2</a>, <a class="iref" href="#rfc.xref.Part1.5">2</a>, <a class="iref" href="#rfc.xref.Part1.6">2</a>, <a class="iref" href="#rfc.xref.Part1.7">2</a>, <a class="iref" href="#rfc.xref.Part1.8">2</a>, <a class="iref" href="#rfc.xref.Part1.9">2</a>, <a class="iref" href="#rfc.xref.Part1.10">2</a>, <a class="iref" href="#rfc.xref.Part1.11">2</a>, <a class="iref" href="#rfc.xref.Part1.12">2</a>, <a class="iref" href="#rfc.xref.Part1.13">4.1</a>, <a class="iref" href="#rfc.xref.Part1.14">4.2</a>, <a class="iref" href="#rfc.xref.Part1.15">4.2.2</a>, <a class="iref" href="#Part1"><b>10.1</b></a>, <a class="iref" href="#rfc.xref.Part1.16">A. 5</a>, <a class="iref" href="#rfc.xref.Part1.17">C.1</a><ul class="ind">1931 <li class="indline1"><em>Part1</em> <a class="iref" href="#rfc.xref.Part1.1">2</a>, <a class="iref" href="#rfc.xref.Part1.2">2</a>, <a class="iref" href="#rfc.xref.Part1.3">2</a>, <a class="iref" href="#rfc.xref.Part1.4">2</a>, <a class="iref" href="#rfc.xref.Part1.5">2</a>, <a class="iref" href="#rfc.xref.Part1.6">2</a>, <a class="iref" href="#rfc.xref.Part1.7">2</a>, <a class="iref" href="#rfc.xref.Part1.8">2</a>, <a class="iref" href="#rfc.xref.Part1.9">2</a>, <a class="iref" href="#rfc.xref.Part1.10">2</a>, <a class="iref" href="#rfc.xref.Part1.11">2</a>, <a class="iref" href="#rfc.xref.Part1.12">2</a>, <a class="iref" href="#rfc.xref.Part1.13">4.1</a>, <a class="iref" href="#rfc.xref.Part1.14">4.2</a>, <a class="iref" href="#rfc.xref.Part1.15">4.2.2</a>, <a class="iref" href="#Part1"><b>10.1</b></a>, <a class="iref" href="#rfc.xref.Part1.16">A.3</a>, <a class="iref" href="#rfc.xref.Part1.17">A.6</a>, <a class="iref" href="#rfc.xref.Part1.18">C.1</a><ul class="ind"> 1923 1932 <li class="indline1"><em>Section 2.1</em> <a class="iref" href="#rfc.xref.Part1.1">2</a></li> 1924 1933 <li class="indline1"><em>Section 2.2</em> <a class="iref" href="#rfc.xref.Part1.2">2</a>, <a class="iref" href="#rfc.xref.Part1.3">2</a>, <a class="iref" href="#rfc.xref.Part1.4">2</a>, <a class="iref" href="#rfc.xref.Part1.5">2</a>, <a class="iref" href="#rfc.xref.Part1.6">2</a>, <a class="iref" href="#rfc.xref.Part1.7">2</a>, <a class="iref" href="#rfc.xref.Part1.8">2</a></li> 1925 1934 <li class="indline1"><em>Section 3.2</em> <a class="iref" href="#rfc.xref.Part1.9">2</a>, <a class="iref" href="#rfc.xref.Part1.11">2</a></li> 1935 <li class="indline1"><em>Section 3.3.1</em> <a class="iref" href="#rfc.xref.Part1.16">A.3</a></li> 1926 1936 <li class="indline1"><em>Section 4.2</em> <a class="iref" href="#rfc.xref.Part1.12">2</a></li> 1927 1937 <li class="indline1"><em>Section 4.3</em> <a class="iref" href="#rfc.xref.Part1.14">4.2</a></li> 1928 1938 <li class="indline1"><em>Section 4.4</em> <a class="iref" href="#rfc.xref.Part1.15">4.2.2</a></li> 1929 1939 <li class="indline1"><em>Section 8.2</em> <a class="iref" href="#rfc.xref.Part1.10">2</a>, <a class="iref" href="#rfc.xref.Part1.13">4.1</a></li> 1930 <li class="indline1"><em>Section 8.7</em> <a class="iref" href="#rfc.xref.Part1.1 6">A.5</a></li>1940 <li class="indline1"><em>Section 8.7</em> <a class="iref" href="#rfc.xref.Part1.17">A.6</a></li> 1931 1941 </ul> 1932 1942 </li> … … 1981 1991 <li class="indline1"><em>RFC2277</em> <a class="iref" href="#rfc.xref.RFC2277.1">3.1</a>, <a class="iref" href="#RFC2277"><b>10.2</b></a></li> 1982 1992 <li class="indline1"><em>RFC2388</em> <a class="iref" href="#rfc.xref.RFC2388.1">3.3.2</a>, <a class="iref" href="#RFC2388"><b>10.2</b></a></li> 1983 <li class="indline1"><em>RFC2557</em> <a class="iref" href="#RFC2557"><b>10.2</b></a>, <a class="iref" href="#rfc.xref.RFC2557.1">A. 6</a>, <a class="iref" href="#rfc.xref.RFC2557.2">C.1</a></li>1993 <li class="indline1"><em>RFC2557</em> <a class="iref" href="#RFC2557"><b>10.2</b></a>, <a class="iref" href="#rfc.xref.RFC2557.1">A.7</a>, <a class="iref" href="#rfc.xref.RFC2557.2">C.1</a></li> 1984 1994 <li class="indline1"><em>RFC2616</em> <a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#RFC2616"><b>10.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.2">D.1</a></li> 1985 1995 <li class="indline1"><em>RFC3629</em> <a class="iref" href="#rfc.xref.RFC3629.1">3.1</a>, <a class="iref" href="#RFC3629"><b>10.2</b></a></li> -
draft-ietf-httpbis/latest/p3-payload.xml
r382 r385 29 29 <!ENTITY message-headers "<xref target='Part1' x:rel='#message.headers' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 30 30 <!ENTITY multipart-byteranges "<xref target='Part5' x:rel='#internet.media.type.multipart.byteranges' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 31 <!ENTITY full-date "<xref target='Part1' x:rel='#full.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 31 32 <!ENTITY uri "<xref target='Part1' x:rel='#uri' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 32 33 ]> … … 2425 2426 </section> 2426 2427 2428 2429 <section title="Conversion of Date Formats" anchor="conversion.of.date.formats"> 2430 <t> 2431 HTTP/1.1 uses a restricted set of date formats (&full-date;) to 2432 simplify the process of date comparison. Proxies and gateways from 2433 other protocols &SHOULD; ensure that any Date header field present in a 2434 message conforms to one of the HTTP/1.1 formats and rewrite the date 2435 if necessary. 2436 </t> 2437 </section> 2438 2427 2439 <section title="Introduction of Content-Encoding" anchor="introduction.of.content-encoding"> 2428 2440 <t> … … 2757 2769 <section title="Since draft-ietf-httpbis-p3-payload-05" anchor="changes.since.05"> 2758 2770 <t> 2771 Closed issues: 2772 <list style="symbols"> 2773 <t> 2774 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/118"/>: 2775 "Join "Differences Between HTTP Entities and RFC 2045 Entities"?" 2776 </t> 2777 </list> 2759 2778 </t> 2760 2779 </section>
Note: See TracChangeset
for help on using the changeset viewer.
