Changeset 1534 for draft-ietf-httpbis/latest
- Timestamp:
- 08/02/12 08:25:34 (11 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r1528 r1534 460 460 } 461 461 @bottom-center { 462 content: "Expires August 1 0, 2012";462 content: "Expires August 11, 2012"; 463 463 } 464 464 @bottom-right { … … 512 512 <meta name="dct.creator" content="Reschke, J. F."> 513 513 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 514 <meta name="dct.issued" scheme="ISO8601" content="2012-02-0 7">514 <meta name="dct.issued" scheme="ISO8601" content="2012-02-08"> 515 515 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 516 516 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request header fields, response status codes, and response header fields."> … … 543 543 </tr> 544 544 <tr> 545 <td class="left">Expires: August 1 0, 2012</td>545 <td class="left">Expires: August 11, 2012</td> 546 546 <td class="right">HP</td> 547 547 </tr> … … 596 596 <tr> 597 597 <td class="left"></td> 598 <td class="right">February 7, 2012</td>598 <td class="right">February 8, 2012</td> 599 599 </tr> 600 600 </tbody> … … 626 626 in progress”. 627 627 </p> 628 <p>This Internet-Draft will expire on August 1 0, 2012.</p>628 <p>This Internet-Draft will expire on August 11, 2012.</p> 629 629 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 630 630 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1878 1878 <p id="rfc.section.7.3.p.4">A Location header field on a 3xx response indicates that a client <em class="bcp14">MAY</em> automatically redirect to the URI provided; see <a href="#header.location" id="rfc.xref.header.location.3" title="Location">Section 9.5</a>. 1879 1879 </p> 1880 <p id="rfc.section.7.3.p.5">Clients <em class="bcp14">SHOULD</em> detect and intervene in cyclical redirections (i.e., "infinite" redirection loops). 1881 </p> 1882 <div class="note" id="rfc.section.7.3.p.6"> 1880 <p id="rfc.section.7.3.p.5">Note that for methods not known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section 6.1.1</a>, automatic redirection needs to done with care, since the redirect might change the conditions under which the request was 1881 issued. 1882 </p> 1883 <p id="rfc.section.7.3.p.6">Clients <em class="bcp14">SHOULD</em> detect and intervene in cyclical redirections (i.e., "infinite" redirection loops). 1884 </p> 1885 <div class="note" id="rfc.section.7.3.p.7"> 1883 1886 <p> <b>Note:</b> An earlier version of this specification recommended a maximum of five redirections (<a href="#RFC2068" id="rfc.xref.RFC2068.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>, <a href="http://tools.ietf.org/html/rfc2068#section-10.3">Section 10.3</a>). Content developers need to be aware that some clients might implement such a fixed limitation. 1884 1887 </p> … … 1910 1913 the new URI(s). 1911 1914 </p> 1912 <p id="rfc.section.7.3.2.p.4">If the 301 status code is received in response to a request method that is known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section 6.1.1</a>, then the request <em class="bcp14">MAY</em> be automatically redirected by the user agent without confirmation. Otherwise, the user agent <em class="bcp14">MUST NOT</em> automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which 1913 the request was issued. 1914 </p> 1915 <div class="note" id="rfc.section.7.3.2.p.5"> 1915 <div class="note" id="rfc.section.7.3.2.p.4"> 1916 1916 <p> <b>Note:</b> For historic reasons, user agents <em class="bcp14">MAY</em> change the request method from POST to GET for the subsequent request. If this behavior is undesired, status code 307 (Temporary 1917 1917 Redirect) can be used instead. … … 1926 1926 the new URI(s). 1927 1927 </p> 1928 <p id="rfc.section.7.3.3.p.3">If the 302 status code is received in response to a request method that is known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section 6.1.1</a>, then the request <em class="bcp14">MAY</em> be automatically redirected by the user agent without confirmation. Otherwise, the user agent <em class="bcp14">MUST NOT</em> automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which 1929 the request was issued. 1930 </p> 1931 <div class="note" id="rfc.section.7.3.3.p.4"> 1928 <div class="note" id="rfc.section.7.3.3.p.3"> 1932 1929 <p> <b>Note:</b> For historic reasons, user agents <em class="bcp14">MAY</em> change the request method from POST to GET for the subsequent request. If this behavior is undesired, status code 307 (Temporary 1933 1930 Redirect) can be used instead. … … 1972 1969 the new URI(s). 1973 1970 </p> 1974 <p id="rfc.section.7.3.7.p.3">If the 307 status code is received in response to a request method that is known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section 6.1.1</a>, then the request <em class="bcp14">MAY</em> be automatically redirected by the user agent without confirmation. Otherwise, the user agent <em class="bcp14">MUST NOT</em> automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which 1975 the request was issued. 1976 </p> 1977 <div class="note" id="rfc.section.7.3.7.p.4"> 1971 <div class="note" id="rfc.section.7.3.7.p.3"> 1978 1972 <p> <b>Note:</b> This status code is similar to 302 Found, except that it does not allow rewriting the request method from POST to GET. This 1979 1973 specification defines no equivalent counterpart for 301 Moved Permanently. … … 3056 3050 <p id="rfc.section.A.p.5">Broadened the definition of 203 (Non-Authoritative Information) to include cases of payload transformations as well. (<a href="#status.203" id="rfc.xref.status.203.3" title="203 Non-Authoritative Information">Section 7.2.4</a>) 3057 3051 </p> 3058 <p id="rfc.section.A.p.6"> Removed the normative requirements on response payloads for status codes 301, 302, and 307. (<a href="#status.3xx" title="Redirection 3xx">Section 7.3</a>)3052 <p id="rfc.section.A.p.6">Status codes 301, 302, and 307: removed the normative requirements on both response payloads and user interaction. (<a href="#status.3xx" title="Redirection 3xx">Section 7.3</a>) 3059 3053 </p> 3060 3054 <p id="rfc.section.A.p.7">Failed to consider that there are many other request methods that are safe to automatically redirect, and further that the … … 3496 3490 <p id="rfc.section.C.20.p.1">Closed issues: </p> 3497 3491 <ul> 3492 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/238">http://tools.ietf.org/wg/httpbis/trac/ticket/238</a>>: "Requirements for user intervention during redirects" 3493 </li> 3498 3494 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/302">http://tools.ietf.org/wg/httpbis/trac/ticket/302</a>>: "Misplaced text on connection handling in p2" 3499 3495 </li> -
draft-ietf-httpbis/latest/p2-semantics.xml
r1526 r1534 1695 1695 </t> 1696 1696 <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> 1697 1702 Clients &SHOULD; detect and intervene in cyclical redirections (i.e., 1698 1703 "infinite" redirection loops). … … 1758 1763 hyperlink to the new URI(s). 1759 1764 </t> 1760 <t>1761 If the 301 status code is received in response to a request method1762 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 without1764 confirmation. Otherwise, the user agent &MUST-NOT; automatically redirect the1765 request unless it can be confirmed by the user, since this might1766 change the conditions under which the request was issued.1767 </t>1768 1765 <x:note> 1769 1766 <t> … … 1788 1785 response. A response payload can contain a short hypertext note with a 1789 1786 hyperlink to the new URI(s). 1790 </t>1791 <t>1792 If the 302 status code is received in response to a request method1793 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 without1795 confirmation. Otherwise, the user agent &MUST-NOT; automatically redirect the1796 request unless it can be confirmed by the user, since this might1797 change the conditions under which the request was issued.1798 1787 </t> 1799 1788 <x:note> … … 1879 1868 response. A response payload can contain a short hypertext note with a 1880 1869 hyperlink to the new URI(s). 1881 </t>1882 <t>1883 If the 307 status code is received in response to a request method1884 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 without1886 confirmation. Otherwise, the user agent &MUST-NOT; automatically redirect the1887 request unless it can be confirmed by the user, since this might1888 change the conditions under which the request was issued.1889 1870 </t> 1890 1871 <x:note> … … 3898 3879 </t> 3899 3880 <t> 3900 Removed the normative requirements on response payloads for status codes3901 301, 302, and 307.3881 Status codes 301, 302, and 307: removed the normative requirements on both 3882 response payloads and user interaction. 3902 3883 (<xref target="status.3xx"/>) 3903 3884 </t> … … 4673 4654 <list style="symbols"> 4674 4655 <t> 4656 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/238"/>: 4657 "Requirements for user intervention during redirects" 4658 </t> 4659 <t> 4675 4660 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/302"/>: 4676 4661 "Misplaced text on connection handling in p2"
Note: See TracChangeset
for help on using the changeset viewer.