Ignore:
Timestamp:
Feb 8, 2012, 12:25:34 AM (8 years ago)
Author:
julian.reschke@…
Message:

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

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1526 r1534  
    16951695</t>
    16961696<t>
     1697   Note that for methods not known to be "safe", as defined in <xref target="safe.methods"/>,
     1698   automatic redirection needs to done with care, since the redirect might
     1699   change the conditions under which the request was issued.
     1700</t>
     1701<t>
    16971702   Clients &SHOULD; detect and intervene in cyclical redirections (i.e.,
    16981703   "infinite" redirection loops).
     
    17581763   hyperlink to the new URI(s).
    17591764</t>
    1760 <t>
    1761    If the 301 status code is received in response to a request method
    1762    that is known to be "safe", as defined in <xref target="safe.methods"/>,
    1763    then the request &MAY; be automatically redirected by the user agent without
    1764    confirmation.  Otherwise, the user agent &MUST-NOT; automatically redirect the
    1765    request unless it can be confirmed by the user, since this might
    1766    change the conditions under which the request was issued.
    1767 </t>
    17681765<x:note>
    17691766  <t>
     
    17881785   response. A response payload can contain a short hypertext note with a
    17891786   hyperlink to the new URI(s).
    1790 </t>
    1791 <t>
    1792    If the 302 status code is received in response to a request method
    1793    that is known to be "safe", as defined in <xref target="safe.methods"/>,
    1794    then the request &MAY; be automatically redirected by the user agent without
    1795    confirmation.  Otherwise, the user agent &MUST-NOT; automatically redirect the
    1796    request unless it can be confirmed by the user, since this might
    1797    change the conditions under which the request was issued.
    17981787</t>
    17991788<x:note>
     
    18791868   response. A response payload can contain a short hypertext note with a
    18801869   hyperlink to the new URI(s).
    1881 </t>
    1882 <t>
    1883    If the 307 status code is received in response to a request method
    1884    that is known to be "safe", as defined in <xref target="safe.methods"/>,
    1885    then the request &MAY; be automatically redirected by the user agent without
    1886    confirmation.  Otherwise, the user agent &MUST-NOT; automatically redirect the
    1887    request unless it can be confirmed by the user, since this might
    1888    change the conditions under which the request was issued.
    18891870</t>
    18901871<x:note>
     
    38983879</t>
    38993880<t>
    3900   Removed the normative requirements on response payloads for status codes
    3901   301, 302, and 307.
     3881  Status codes 301, 302, and 307: removed the normative requirements on both
     3882  response payloads and user interaction.
    39023883  (<xref target="status.3xx"/>)
    39033884</t>
     
    46734654  <list style="symbols">
    46744655    <t>
     4656      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/238"/>:
     4657      "Requirements for user intervention during redirects"
     4658    </t>
     4659    <t>
    46754660      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/302"/>:
    46764661      "Misplaced text on connection handling in p2"
Note: See TracChangeset for help on using the changeset viewer.