Changeset 2024 for draft-ietf-httpbis/latest/p1-messaging.xml

Timestamp:

Nov 29, 2012, 3:51:24 PM (7 years ago)

Author:

mnot@…

Message:

More adjustments to "Changes from RFC2616", based upon the issues list.

File:

• draft-ietf-httpbis/latest/p1-messaging.xml (modified) (6 diffs)

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

@@ -4719 +4719 @@
 <section title="Changes from RFC 2616" anchor="changes.from.rfc.2616">
 <t>
+  HTTP's approach to error handling has been explained.
+  (<xref target="conformance"/>)
+</t>
+<t>
+  The expectation to support HTTP/0.9 requests has been removed.
+</t>
+<t>
+  The term "Effective Request URI" has been introduced.
+  (<xref target="effective.request.uri" />)
+</t>
+<t>
+  HTTP messages can be (and often are) buffered by implementations; despite
+  it sometimes being available as a stream, HTTP is fundamentally a
+  message-oriented protocol.
+  (<xref target="http.message" />)
+</t>
+<t>
+  Minimum supported sizes for various protocol elements have been 
+  suggested, to improve interoperability.
+</t>
+<t>
+  Header fields that span multiple lines ("line folding") are deprecated.
+  (<xref target="field.parsing" />)
+</t>
+<t>
   The HTTP-version ABNF production has been clarified to be case-sensitive.
   Additionally, version numbers has been restricted to single digits, due
@@ -4726 +4751 @@
 </t>
 <t>
-  The "HTTPS" URI scheme is now defined by this specification; previously,
+  The HTTPS URI scheme is now defined by this specification; previously,
   it was done in  <xref target="RFC2818" x:fmt="of" x:sec="2.4"/>.
   (<xref target="https.uri"/>)
+</t>
+<t>
+  The HTTPS URI scheme implies end-to-end security.
+  (<xref target="https.uri"/>)
+</t>
+<t>
+  Userinfo (i.e., username and password) are now disallowed in HTTP and
+  HTTPS URIs, because of security issues related to their transmission on the
+  wire.
+  (<xref target="http.uri" />)
 </t>
 <t>
@@ -4746 +4781 @@
 </t>
 <t>  
-  The NUL octet is no longer allowed in comment and quoted-string text.
+  The NUL octet is no longer allowed in comment and quoted-string text, and
+  handling of backslash-escaping in them has been clarified.
   (<xref target="field.components"/>)
 </t>  
@@ -4768 +4804 @@
   (Sections <xref format="counter" target="message.body"/> and
   <xref format="counter" target="transfer.codings"/>)
+</t>
+<t>
+  The algorithm for determining the message body length has been clarified
+  to indicate all of the special cases (e.g., driven by methods or status
+  codes) that affect it, and that new protocol elements cannot define such
+  special cases.
+  (<xref target="message.body.length"/>)
 </t>
 <t>
@@ -4837 +4880 @@
 </t>
 <t>
+  The meaning of the "deflate" content coding has been clarified.
+  (<xref target="deflate.coding" />)
+</t>
+<t>
   This specification now defines the Upgrade Token Registry, previously
   defined in <xref target="RFC2817" x:fmt="of" x:sec="7.2"/>.
@@ -4842 +4889 @@
 </t>
 <t>
-  Empty list elements in list productions have been deprecated.
+  Empty list elements in list productions (e.g., a list header containing 
+  ", ,") have been deprecated.
   (<xref target="abnf.extension"/>)
+</t>
+<t>
+  Issues with the Keep-Alive and Proxy-Connection headers in requests
+  are pointed out, with use of the latter being discouraged altogether.
+  (<xref target="compatibility.with.http.1.0.persistent.connections" />)
 </t>
 </section>