Ignore:
Timestamp:
Aug 24, 2009, 12:37:27 AM (10 years ago)
Author:
julian.reschke@…
Message:

remove expectations on HTTP/0.9 support (see #184)

File:
1 edited

Legend:

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

    r684 r685  
    400400      <meta name="DC.Creator" content="Reschke, J. F.">
    401401      <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">
    403403      <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616">
    404404      <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 &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 1 provides an overview of HTTP and its associated terminology, defines the &#34;http&#34; and &#34;https&#34; Uniform Resource Identifier (URI) schemes, defines the generic message syntax and parsing requirements for HTTP message frames, and describes general security concerns for implementations.">
     
    436436         </tr>
    437437         <tr>
    438             <td class="header left">Expires: February 17, 2010</td>
     438            <td class="header left">Expires: February 25, 2010</td>
    439439            <td class="header right">H. Frystyk</td>
    440440         </tr>
     
    485485         <tr>
    486486            <td class="header left"></td>
    487             <td class="header right">August 16, 2009</td>
     487            <td class="header right">August 24, 2009</td>
    488488         </tr>
    489489      </table>
     
    509509      <p>The list of Internet-Draft Shadow Directories can be accessed at &lt;<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>&gt;.
    510510      </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>
    512512      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    513513      <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    27132713      </p>
    27142714      <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 commercial HTTP/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:
    27172717      </p>
    27182718      <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>
    27212720         <li>respond appropriately with a message in the same major version used by the client.</li>
    27222721      </ul>
    27232722      <p id="rfc.section.B.p.4">And we would expect HTTP/1.1 clients to: </p>
    27242723      <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>
    27272725      </ul>
    27282726      <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
     
    32063204         </li>
    32073205         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/172">http://tools.ietf.org/wg/httpbis/trac/ticket/172</a>&gt;: "take over HTTP Upgrade Token Registry"
     3206         </li>
     3207         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/184">http://tools.ietf.org/wg/httpbis/trac/ticket/184</a>&gt;: "HTTP/0.9 support"
    32083208         </li>
    32093209         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/188">http://tools.ietf.org/wg/httpbis/trac/ticket/188</a>&gt;: "pick IANA policy (RFC5226) for Transfer Coding / Content Coding"
Note: See TracChangeset for help on using the changeset viewer.