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

Timestamp:

21/07/09 11:28:41 (13 years ago)

Author:

julian.reschke@…

Message:

Resolve #140: rephrase note so that it becomes clear that the described change already happened in RFC2616, also add 303/307 to the "changes from RFC2068" section (closes #140)

File:

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

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

@@ -1337 +1337 @@
 <x:note>
   <t>
-    <x:h>Note:</x:h> <xref target="RFC1945"/> and <xref target="RFC2068"/> specify that the client is not allowed
-    to change the method on the redirected request.  However, most
-    existing user agent implementations treat 302 as if it were a 303
-    response, performing a GET on the Location field-value regardless
-    of the original request method. The status codes 303 and 307 have
-    been added for servers that wish to make unambiguously clear which
-    kind of reaction is expected of the client.
+    <x:h>Note:</x:h> HTTP/1.0 (<xref target="RFC1945" x:fmt="," x:sec="9.3"/>)
+    and the first version of HTTP/1.1 (<xref target="RFC2068" x:fmt="," x:sec ="10.3.3"/>)
+    specify that the client is not allowed to change the method on the
+    redirected request.  However, most existing user agent implementations
+    treat 302 as if it were a 303 response, performing a GET on the Location
+    field-value regardless of the original request method. Therefore, a 
+    previous version of this specification
+    (<xref target="RFC2616" x:fmt="," x:sec="10.3.3"/>) has added the 
+    status codes
+    <xref target="status.303" format="none">303</xref> and
+    <xref target="status.307" format="none">307</xref> for servers that wish
+    to make unambiguously clear which kind of reaction is expected of the
+    client.
   </t>
 </x:note>
@@ -3141 +3147 @@
 </t>
 <t>
+   303 (See Also) and 307 (Temporary Redirect) added to address user agent
+   failure to implement status code 302 properly.
+   (Section <xref target="status.303" format="counter"/> and <xref target="status.307" format="counter"/>)
+</t>
+<t>
    Rewrite of message transmission requirements to make it much harder
    for implementors to get it wrong, as the consequences of errors here
@@ -3605 +3616 @@
 <section title="Since draft-ietf-httpbis-p2-semantics-07" anchor="changes.since.07">
 <t>
-  None.
+  Closed issues:
+  <list style="symbols"> 
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/140"/>:
+      "update note citing RFC 1945 and 2068"
+    </t>
+  </list>
 </t>
 </section>