Changeset 2023 for draft-ietf-httpbis/latest/p2-semantics.xml

Timestamp:

Nov 28, 2012, 8:28:13 PM (7 years ago)

Author:

mnot@…

Message:

Update Changes from RFC2626, from issues list.

File:

• draft-ietf-httpbis/latest/p2-semantics.xml (modified) (4 diffs)

draft-ietf-httpbis/latest/p2-semantics.xml

@@ -5678 +5678 @@
 </t>
 <t>
-  The "<x:ref>Max-Forwards</x:ref>" header field is now restricted to the
+  The requirements upon and semantics of CONNECT request and response bodies 
+  have been clarified.
+  (<xref target="CONNECT"/>)
+</t>
+<t>
+  The <x:ref>OPTIONS</x:ref> and <x:ref>TRACE</x:ref> request methods are
+  now defined as being safe.
+  (<xref target="OPTIONS"/> and <xref target="TRACE"/>)
+</t>
+<t>
+  The <x:ref>Max-Forwards</x:ref> header field is now restricted to the
   OPTIONS and TRACE methods (previously, extension methods could have used it
   as well).
@@ -5696 +5706 @@
 </t>
 <t>
-  "<x:ref>Referer</x:ref>" can now hoave a field value of "about:blank" as an
-  alternative to not sending a Referer header field.
+  The <x:ref>Referer</x:ref> header field can now have a value of
+  "about:blank" as an alternative to not sending a Referer header field.
   (<xref target="header.referer"/>)
+</t>
+<t>
+  The <x:ref>201 (Created)</x:ref> status code can indicate that more than
+  one resource has been created (as well as just one). 
 </t>
 <t>
@@ -5716 +5730 @@
   based upon the request method semantics.
   (<xref target="status.3xx"/>)
+</t>
+<t>
+  The syntax of the <x:ref>Location</x:ref> header field has been corrected
+  to allow URI references (including relative references and fragments), along
+  with some clarifications as to when use of fragments would not be
+  appropriate.
+  (<xref target="header.location"/>)
+</t>
+<t>
+  The 303 (See Other) status code is now cacheable, if explicit freshness
+  information is available.
+  (<xref target="status.303" />)
 </t>
 <t>
@@ -5733 +5759 @@
 </t>
 <t>
+  The <x:ref>400 (Bad Request)</x:ref> status code has been made more generic;
+  it isn't limited to syntax errors.
+  (<xref target="status.400"/>)
+</t>
+<t>
+  The <x:ref>403 (Forbidden)</x:ref> status code has been clarified, 
+  especially with regards to authentication.
+  (<xref target="status.403"/>)
+</t>
+<t>
   The <x:ref>426 (Upgrade Required)</x:ref> status code has been incorporated
   from <xref target="RFC2817"/>.
   (<xref target="status.426"/>)
-</t>
-<t>
-  The syntax of the <x:ref>Location</x:ref> header field has been corrected
-  to allow URI references (including relative references and fragments), along
-  with some clarifications as to when use of fragments would not be
-  appropriate.
-  (<xref target="header.location"/>)
 </t>
 <t>