Changeset 685 for draft-ietf-httpbis
- Timestamp:
- 24/08/09 07:37:27 (13 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r684 r685 400 400 <meta name="DC.Creator" content="Reschke, J. F."> 401 401 <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 402 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-08- 16">402 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-08-24"> 403 403 <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> 404 404 <meta name="DC.Description.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."> … … 436 436 </tr> 437 437 <tr> 438 <td class="header left">Expires: February 17, 2010</td>438 <td class="header left">Expires: February 25, 2010</td> 439 439 <td class="header right">H. Frystyk</td> 440 440 </tr> … … 485 485 <tr> 486 486 <td class="header left"></td> 487 <td class="header right">August 16, 2009</td>487 <td class="header right">August 24, 2009</td> 488 488 </tr> 489 489 </table> … … 509 509 <p>The list of Internet-Draft Shadow Directories can be accessed at <<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>>. 510 510 </p> 511 <p>This Internet-Draft will expire in February 17, 2010.</p>511 <p>This Internet-Draft will expire in February 25, 2010.</p> 512 512 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 513 513 <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 2713 2713 </p> 2714 2714 <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 2715 designed, however, to make supporting previous versions easy. It is worth noting that, at the time of composing this specification 2716 (1996), we would expect commercialHTTP/1.1 servers to:2715 designed, however, to make supporting previous versions easy. It is worth noting that, at the time of composing this specification, 2716 we would expect general-purpose HTTP/1.1 servers to: 2717 2717 </p> 2718 2718 <ul> 2719 <li>recognize the format of the Request-Line for HTTP/0.9, 1.0, and 1.1 requests;</li> 2720 <li>understand any valid request in the format of HTTP/0.9, 1.0, or 1.1;</li> 2719 <li>understand any valid request in the format of HTTP/1.0 and 1.1;</li> 2721 2720 <li>respond appropriately with a message in the same major version used by the client.</li> 2722 2721 </ul> 2723 2722 <p id="rfc.section.B.p.4">And we would expect HTTP/1.1 clients to: </p> 2724 2723 <ul> 2725 <li>recognize the format of the Status-Line for HTTP/1.0 and 1.1 responses;</li> 2726 <li>understand any valid response in the format of HTTP/0.9, 1.0, or 1.1.</li> 2724 <li>understand any valid response in the format of HTTP/1.0 or 1.1.</li> 2727 2725 </ul> 2728 2726 <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 … … 3206 3204 </li> 3207 3205 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/172">http://tools.ietf.org/wg/httpbis/trac/ticket/172</a>>: "take over HTTP Upgrade Token Registry" 3206 </li> 3207 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/184">http://tools.ietf.org/wg/httpbis/trac/ticket/184</a>>: "HTTP/0.9 support" 3208 3208 </li> 3209 3209 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/188">http://tools.ietf.org/wg/httpbis/trac/ticket/188</a>>: "pick IANA policy (RFC5226) for Transfer Coding / Content Coding" -
draft-ietf-httpbis/latest/p1-messaging.xml
r684 r685 4461 4461 compliance with previous versions. HTTP/1.1 was deliberately 4462 4462 designed, however, to make supporting previous versions easy. It is 4463 worth noting that, at the time of composing this specification 4464 (1996), we would expect commercialHTTP/1.1 servers to:4463 worth noting that, at the time of composing this specification, we would 4464 expect general-purpose HTTP/1.1 servers to: 4465 4465 <list style="symbols"> 4466 <t>recognize the format of the Request-Line for HTTP/0.9, 1.0, and 4467 1.1 requests;</t> 4468 4469 <t>understand any valid request in the format of HTTP/0.9, 1.0, or 4466 <t>understand any valid request in the format of HTTP/1.0 and 4470 4467 1.1;</t> 4471 4468 … … 4477 4474 And we would expect HTTP/1.1 clients to: 4478 4475 <list style="symbols"> 4479 <t>recognize the format of the Status-Line for HTTP/1.0 and 1.1 4480 responses;</t> 4481 4482 <t>understand any valid response in the format of HTTP/0.9, 1.0, or 4476 <t>understand any valid response in the format of HTTP/1.0 or 4483 4477 1.1.</t> 4484 4478 </list> … … 5262 5256 </t> 5263 5257 <t> 5258 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/184"/>: 5259 "HTTP/0.9 support" 5260 </t> 5261 <t> 5264 5262 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/188"/>: 5265 5263 "pick IANA policy (RFC5226) for Transfer Coding / Content Coding"
Note: See TracChangeset
for help on using the changeset viewer.