Changeset 1053
- Timestamp:
- 23/10/10 07:33:38 (12 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r1052 r1053 404 404 <meta name="dct.creator" content="Reschke, J. F."> 405 405 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 406 <meta name="dct.issued" scheme="ISO8601" content="2010-10-2 2">406 <meta name="dct.issued" scheme="ISO8601" content="2010-10-23"> 407 407 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 408 408 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 1 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 1 provides an overview of HTTP and its associated terminology, defines the "http" and "https" Uniform Resource Identifier (URI) schemes, defines the generic message syntax and parsing requirements for HTTP message frames, and describes general security concerns for implementations."> … … 435 435 </tr> 436 436 <tr> 437 <td class="left">Expires: April 2 5, 2011</td>437 <td class="left">Expires: April 26, 2011</td> 438 438 <td class="right">HP</td> 439 439 </tr> … … 488 488 <tr> 489 489 <td class="left"></td> 490 <td class="right">October 2 2, 2010</td>490 <td class="right">October 23, 2010</td> 491 491 </tr> 492 492 </tbody> … … 516 516 in progress”. 517 517 </p> 518 <p>This Internet-Draft will expire on April 2 5, 2011.</p>518 <p>This Internet-Draft will expire on April 26, 2011.</p> 519 519 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 520 520 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1635 1635 described in <a href="#header.te" id="rfc.xref.header.te.2" title="TE">Section 9.5</a>; or, 1636 1636 </li> 1637 <li>the server is the origin server for the response, the trailer fields consist entirely of optional metadata, and the recipient 1638 could use the message (in a manner acceptable to the origin server) without receiving this metadata. In other words, the origin 1639 server is willing to accept the possibility that the trailer fields might be silently discarded along the path to the client. 1637 <li>the trailer fields consist entirely of optional metadata, and the recipient could use the message (in a manner acceptable 1638 to the server where the field originated) without receiving it. In other words, the server that generated the header (often 1639 but not always the origin server) is willing to accept the possibility that the trailer fields might be silently discarded 1640 along the path to the client. 1640 1641 </li> 1641 1642 </ol> … … 3469 3470 </ul> 3470 3471 <h2 id="rfc.section.D.14"><a href="#rfc.section.D.14">D.14</a> <a id="changes.since.12" href="#changes.since.12">Since draft-ietf-httpbis-p1-messaging-12</a></h2> 3471 <p id="rfc.section.D.14.p.1">None yet.</p> 3472 <p id="rfc.section.D.14.p.1">Closed issues: </p> 3473 <ul> 3474 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/193">http://tools.ietf.org/wg/httpbis/trac/ticket/193</a>>: "Trailer requirements" 3475 </li> 3476 </ul> 3472 3477 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 3473 3478 <p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.B">B</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.K">K</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.N">N</a> <a href="#rfc.index.O">O</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.T">T</a> <a href="#rfc.index.U">U</a> <a href="#rfc.index.V">V</a> -
draft-ietf-httpbis/latest/p1-messaging.xml
r1052 r1053 2086 2086 acceptable in the transfer-coding of the response, as described in 2087 2087 <xref target="header.te"/>; or,</t> 2088 2089 <t>the server is the origin server for the response, the trailer2090 fields consist entirely of optional metadata, and the recipient2091 could use the message (in a manner acceptable to the origin server)2092 without receiving this metadata. In other words, the origin server2093 is willing to accept the possibility that the trailer fields might2094 be silently discardedalong the path to the client.</t>2088 2089 <t>the trailer fields consist entirely of optional metadata, and the 2090 recipient could use the message (in a manner acceptable to the server where 2091 the field originated) without receiving it. In other words, the server that 2092 generated the header (often but not always the origin server) is willing to 2093 accept the possibility that the trailer fields might be silently discarded 2094 along the path to the client.</t> 2095 2095 </list> 2096 2096 </t> … … 5683 5683 <section title="Since draft-ietf-httpbis-p1-messaging-12" anchor="changes.since.12"> 5684 5684 <t> 5685 None yet. 5685 Closed issues: 5686 <list style="symbols"> 5687 <t> 5688 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/193"/>: 5689 "Trailer requirements" 5690 </t> 5691 </list> 5686 5692 </t> 5687 5693 </section>
Note: See TracChangeset
for help on using the changeset viewer.