Changeset 685 for draft-ietf-httpbis

Timestamp:

24/08/09 07:37:27 (13 years ago)

Author:

julian.reschke@…

Message:

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

Location:

draft-ietf-httpbis/latest

Files:

• p1-messaging.html (modified) (6 diffs)
• p1-messaging.xml (modified) (3 diffs)

draft-ietf-httpbis/latest/p1-messaging.html

@@ -400 +400 @@
       <meta name="DC.Creator" content="Reschke, J. F.">
       <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
-      <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-08-16">
+      <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-08-24">
       <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616">
       <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.">
@@ -436 +436 @@
          </tr>
          <tr>
-            <td class="header left">Expires: February 17, 2010</td>
+            <td class="header left">Expires: February 25, 2010</td>
             <td class="header right">H. Frystyk</td>
          </tr>
@@ -485 +485 @@
          <tr>
             <td class="header left"></td>
-            <td class="header right">August 16, 2009</td>
+            <td class="header right">August 24, 2009</td>
          </tr>
       </table>
@@ -509 +509 @@
       <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;.
       </p>
-      <p>This Internet-Draft will expire in February 17, 2010.</p>
+      <p>This Internet-Draft will expire in February 25, 2010.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -2713 +2713 @@
       </p>
       <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
-         designed, however, to make supporting previous versions easy. It is worth noting that, at the time of composing this specification
-         (1996), we would expect commercial HTTP/1.1 servers to: 
+         designed, however, to make supporting previous versions easy. It is worth noting that, at the time of composing this specification,
+         we would expect general-purpose HTTP/1.1 servers to: 
       </p>
       <ul>
-         <li>recognize the format of the Request-Line for HTTP/0.9, 1.0, and 1.1 requests;</li>
-         <li>understand any valid request in the format of HTTP/0.9, 1.0, or 1.1;</li>
+         <li>understand any valid request in the format of HTTP/1.0 and 1.1;</li>
          <li>respond appropriately with a message in the same major version used by the client.</li>
       </ul>
       <p id="rfc.section.B.p.4">And we would expect HTTP/1.1 clients to: </p>
       <ul>
-         <li>recognize the format of the Status-Line for HTTP/1.0 and 1.1 responses;</li>
-         <li>understand any valid response in the format of HTTP/0.9, 1.0, or 1.1.</li>
+         <li>understand any valid response in the format of HTTP/1.0 or 1.1.</li>
       </ul>
       <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>
          <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"
+         </li>
+         <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"
          </li>
          <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"

draft-ietf-httpbis/latest/p1-messaging.xml

@@ -4461 +4461 @@
    compliance with previous versions. HTTP/1.1 was deliberately
    designed, however, to make supporting previous versions easy. It is
-   worth noting that, at the time of composing this specification
-   (1996), we would expect commercial HTTP/1.1 servers to:
+   worth noting that, at the time of composing this specification, we would
+   expect general-purpose HTTP/1.1 servers to:
   <list style="symbols">
-     <t>recognize the format of the Request-Line for HTTP/0.9, 1.0, and
-        1.1 requests;</t>
-
-     <t>understand any valid request in the format of HTTP/0.9, 1.0, or
+     <t>understand any valid request in the format of HTTP/1.0 and
         1.1;</t>
 
@@ -4477 +4474 @@
    And we would expect HTTP/1.1 clients to:
   <list style="symbols">
-     <t>recognize the format of the Status-Line for HTTP/1.0 and 1.1
-        responses;</t>
-
-     <t>understand any valid response in the format of HTTP/0.9, 1.0, or
+     <t>understand any valid response in the format of HTTP/1.0 or
         1.1.</t>
   </list>
@@ -5262 +5256 @@
     </t>
     <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/184"/>:
+      "HTTP/0.9 support"
+    </t>
+    <t>
       <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/188"/>:
       "pick IANA policy (RFC5226) for Transfer Coding / Content Coding"