Changeset 629
- Timestamp:
- 27/07/09 15:15:31 (13 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r628 r629 1169 1169 </p> 1170 1170 <div class="note"> 1171 <p> <b>Note:</b> previous versions of this specification recommended a maximum of five redirections. Content developers should be aware that 1172 there might be clients that implement such a fixed limitation. 1171 <p> <b>Note:</b> an earlier version of this specification recommended a maximum of five redirections (<a href="#RFC2068" id="rfc.xref.RFC2068.1"><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 should be aware that there might be clients that implement such a fixed limitation. 1173 1172 </p> 1174 1173 </div> … … 1215 1214 </p> 1216 1215 <div class="note"> 1217 <p> <b>Note:</b> HTTP/1.0 (<a href="#RFC1945" id="rfc.xref.RFC1945.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.0">[RFC1945]</cite></a>, <a href="http://tools.ietf.org/html/rfc1945#section-9.3">Section 9.3</a>) and the first version of HTTP/1.1 (<a href="#RFC2068" id="rfc.xref.RFC2068. 1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>, <a href="http://tools.ietf.org/html/rfc2068#section-10.3.3">Section 10.3.3</a>) specify that the client is not allowed to change the method on the redirected request. However, most existing user agent1216 <p> <b>Note:</b> HTTP/1.0 (<a href="#RFC1945" id="rfc.xref.RFC1945.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.0">[RFC1945]</cite></a>, <a href="http://tools.ietf.org/html/rfc1945#section-9.3">Section 9.3</a>) and the first version of HTTP/1.1 (<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.3">Section 10.3.3</a>) specify that the client is not allowed to change the method on the redirected request. However, most existing user agent 1218 1217 implementations treat 302 as if it were a 303 response, performing a GET on the Location field-value regardless of the original 1219 1218 request method. Therefore, a previous version of this specification (<a href="#RFC2616" id="rfc.xref.RFC2616.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="http://tools.ietf.org/html/rfc2616#section-10.3.3">Section 10.3.3</a>) has added the status codes 303 (<a href="#status.303" id="rfc.xref.status.303.2" title="303 See Other">Section 8.3.4</a>) and 307 (<a href="#status.307" id="rfc.xref.status.307.2" title="307 Temporary Redirect">Section 8.3.8</a>) for servers that wish to make unambiguously clear which kind of reaction is expected of the client. … … 2232 2231 <p id="rfc.section.A.1.p.6">Clean up confusion between 403 and 404 responses. (Section <a href="#status.403" id="rfc.xref.status.403.3" title="403 Forbidden">8.4.4</a>, <a href="#status.404" id="rfc.xref.status.404.3" title="404 Not Found">8.4.5</a>, and <a href="#status.410" id="rfc.xref.status.410.3" title="410 Gone">8.4.11</a>) 2233 2232 </p> 2234 <p id="rfc.section.A.1.p.7">The PATCH<span id="rfc.iref.p.3"></span><span id="rfc.iref.m.10"></span>, LINK<span id="rfc.iref.l.2"></span><span id="rfc.iref.m.11"></span>, UNLINK<span id="rfc.iref.u.2"></span><span id="rfc.iref.m.12"></span> methods were defined but not commonly implemented in previous versions of this specification. See <a href="http://tools.ietf.org/html/rfc2068#section-19.6.1">Section 19.6.1</a> of <a href="#RFC2068" id="rfc.xref.RFC2068. 2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>.2233 <p id="rfc.section.A.1.p.7">The PATCH<span id="rfc.iref.p.3"></span><span id="rfc.iref.m.10"></span>, LINK<span id="rfc.iref.l.2"></span><span id="rfc.iref.m.11"></span>, UNLINK<span id="rfc.iref.u.2"></span><span id="rfc.iref.m.12"></span> methods were defined but not commonly implemented in previous versions of this specification. See <a href="http://tools.ietf.org/html/rfc2068#section-19.6.1">Section 19.6.1</a> of <a href="#RFC2068" id="rfc.xref.RFC2068.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>. 2235 2234 </p> 2236 2235 <h2 id="rfc.section.A.2"><a href="#rfc.section.A.2">A.2</a> <a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2> … … 2503 2502 <ul> 2504 2503 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/140">http://tools.ietf.org/wg/httpbis/trac/ticket/140</a>>: "update note citing RFC 1945 and 2068" 2504 </li> 2505 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/182">http://tools.ietf.org/wg/httpbis/trac/ticket/182</a>>: "update note about redirect limit" 2505 2506 </li> 2506 2507 </ul> … … 2735 2736 </ul> 2736 2737 </li> 2737 <li class="indline1"><em>RFC2068</em> <a class="iref" href="#rfc.xref.RFC2068.1">8.3.3</a>, <a class="iref" href="#RFC2068"><b>13.2</b></a>, <a class="iref" href="#rfc.xref.RFC2068.2">A.1</a><ul class="ind"> 2738 <li class="indline1"><em>Section 10.3.3</em> <a class="iref" href="#rfc.xref.RFC2068.1">8.3.3</a></li> 2739 <li class="indline1"><em>Section 19.6.1</em> <a class="iref" href="#rfc.xref.RFC2068.2">A.1</a></li> 2738 <li class="indline1"><em>RFC2068</em> <a class="iref" href="#rfc.xref.RFC2068.1">8.3</a>, <a class="iref" href="#rfc.xref.RFC2068.2">8.3.3</a>, <a class="iref" href="#RFC2068"><b>13.2</b></a>, <a class="iref" href="#rfc.xref.RFC2068.3">A.1</a><ul class="ind"> 2739 <li class="indline1"><em>Section 10.3</em> <a class="iref" href="#rfc.xref.RFC2068.1">8.3</a></li> 2740 <li class="indline1"><em>Section 10.3.3</em> <a class="iref" href="#rfc.xref.RFC2068.2">8.3.3</a></li> 2741 <li class="indline1"><em>Section 19.6.1</em> <a class="iref" href="#rfc.xref.RFC2068.3">A.1</a></li> 2740 2742 </ul> 2741 2743 </li> -
draft-ietf-httpbis/latest/p2-semantics.xml
r628 r629 1242 1242 <x:note> 1243 1243 <t> 1244 <x:h>Note:</x:h> previous versionsof this specification recommended a1245 maximum of five redirections . Content developers should be aware1246 that there might be clients that implement such a fixed1247 limitation.1244 <x:h>Note:</x:h> an earlier version of this specification recommended a 1245 maximum of five redirections (<xref target="RFC2068" x:fmt="," x:sec="10.3"/>). 1246 Content developers should be aware that there might be clients that 1247 implement such a fixed limitation. 1248 1248 </t> 1249 1249 </x:note> … … 3622 3622 "update note citing RFC 1945 and 2068" 3623 3623 </t> 3624 <t> 3625 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/182"/>: 3626 "update note about redirect limit" 3627 </t> 3624 3628 </list> 3625 3629 </t>
Note: See TracChangeset
for help on using the changeset viewer.