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

Timestamp:

08/02/12 08:25:34 (9 years ago)

Author:

julian.reschke@…

Message:

Replace normative requirements on redirect on unsafe methods with prose advice (see #238)

File:

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

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

@@ -1695 +1695 @@
 </t>
 <t>
+   Note that for methods not known to be "safe", as defined in <xref target="safe.methods"/>,
+   automatic redirection needs to done with care, since the redirect might
+   change the conditions under which the request was issued.
+</t>
+<t>
    Clients &SHOULD; detect and intervene in cyclical redirections (i.e.,
    "infinite" redirection loops).
@@ -1758 +1763 @@
    hyperlink to the new URI(s).
 </t>
-<t>
-   If the 301 status code is received in response to a request method
-   that is known to be "safe", as defined in <xref target="safe.methods"/>,
-   then the request &MAY; be automatically redirected by the user agent without
-   confirmation.  Otherwise, the user agent &MUST-NOT; automatically redirect the
-   request unless it can be confirmed by the user, since this might
-   change the conditions under which the request was issued.
-</t>
 <x:note>
   <t>
@@ -1788 +1785 @@
    response. A response payload can contain a short hypertext note with a
    hyperlink to the new URI(s).
-</t>
-<t>
-   If the 302 status code is received in response to a request method
-   that is known to be "safe", as defined in <xref target="safe.methods"/>,
-   then the request &MAY; be automatically redirected by the user agent without
-   confirmation.  Otherwise, the user agent &MUST-NOT; automatically redirect the
-   request unless it can be confirmed by the user, since this might
-   change the conditions under which the request was issued.
 </t>
 <x:note>
@@ -1879 +1868 @@
    response. A response payload can contain a short hypertext note with a
    hyperlink to the new URI(s).
-</t>
-<t>
-   If the 307 status code is received in response to a request method
-   that is known to be "safe", as defined in <xref target="safe.methods"/>,
-   then the request &MAY; be automatically redirected by the user agent without
-   confirmation.  Otherwise, the user agent &MUST-NOT; automatically redirect the
-   request unless it can be confirmed by the user, since this might
-   change the conditions under which the request was issued.
 </t>
 <x:note>
@@ -3898 +3879 @@
 </t>
 <t>
-  Removed the normative requirements on response payloads for status codes
-  301, 302, and 307.
+  Status codes 301, 302, and 307: removed the normative requirements on both
+  response payloads and user interaction.
   (<xref target="status.3xx"/>)
 </t>
@@ -4673 +4654 @@
   <list style="symbols"> 
     <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/238"/>:
+      "Requirements for user intervention during redirects"
+    </t>
+    <t>
       <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/302"/>:
       "Misplaced text on connection handling in p2"