Changeset 1498 for draft-ietf-httpbis/latest/p2-semantics.html
- Timestamp:
- 01/01/12 15:21:56 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r1497 r1498 1782 1782 </p> 1783 1783 </div> 1784 <p id="rfc.section.7.3.p.4">Clients <em class="bcp14">SHOULD</em> detect and intervene in cyclical redirections (i.e., "infinite" redirection loops). 1785 </p> 1786 <div class="note" id="rfc.section.7.3.p.5"> 1784 <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>. 1785 </p> 1786 <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). 1787 </p> 1788 <div class="note" id="rfc.section.7.3.p.6"> 1787 1789 <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. 1788 1790 </p> … … 2755 2757 <td class="left">http</td> 2756 2758 <td class="left">standard</td> 2757 <td class="left"> <a href="#header.location" id="rfc.xref.header.location. 3" title="Location">Section 9.5</a>2759 <td class="left"> <a href="#header.location" id="rfc.xref.header.location.4" title="Location">Section 9.5</a> 2758 2760 </td> 2759 2761 </tr> … … 3013 3015 <p id="rfc.section.A.p.12">Correct syntax of Location header field to allow URI references (including relative references and fragments), as referred 3014 3016 symbol "absoluteURI" wasn't what was expected, and add some clarifications as to when use of fragments would not be appropriate. 3015 (<a href="#header.location" id="rfc.xref.header.location. 4" title="Location">Section 9.5</a>)3017 (<a href="#header.location" id="rfc.xref.header.location.5" title="Location">Section 9.5</a>) 3016 3018 </p> 3017 3019 <p id="rfc.section.A.p.13">Restrict Max-Forwards header field to OPTIONS and TRACE (previously, extension methods could have used it as well). (<a href="#header.max-forwards" id="rfc.xref.header.max-forwards.5" title="Max-Forwards">Section 9.6</a>) … … 3420 3422 </li> 3421 3423 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/312">http://tools.ietf.org/wg/httpbis/trac/ticket/312</a>>: "should there be a permanent variant of 307" 3424 </li> 3425 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/325">http://tools.ietf.org/wg/httpbis/trac/ticket/325</a>>: "When are Location's semantics triggered?" 3422 3426 </li> 3423 3427 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/327">http://tools.ietf.org/wg/httpbis/trac/ticket/327</a>>: "'expect' grammar missing OWS" … … 3566 3570 <li>Expect <a href="#rfc.xref.header.expect.1">3.2</a>, <a href="#rfc.xref.header.expect.2">7.4.18</a>, <a href="#rfc.iref.h.4"><b>9.3</b></a>, <a href="#rfc.xref.header.expect.3">10.3</a>, <a href="#rfc.xref.header.expect.4">A</a></li> 3567 3571 <li>From <a href="#rfc.xref.header.from.1">3.2</a>, <a href="#rfc.iref.h.5"><b>9.4</b></a>, <a href="#rfc.xref.header.from.2">10.3</a></li> 3568 <li>Location <a href="#rfc.xref.header.location.1">3.3</a>, <a href="#rfc.xref.header.location.2">6.5</a>, <a href="#rfc. iref.h.6"><b>9.5</b></a>, <a href="#rfc.xref.header.location.3">10.3</a>, <a href="#rfc.xref.header.location.4">A</a></li>3572 <li>Location <a href="#rfc.xref.header.location.1">3.3</a>, <a href="#rfc.xref.header.location.2">6.5</a>, <a href="#rfc.xref.header.location.3">7.3</a>, <a href="#rfc.iref.h.6"><b>9.5</b></a>, <a href="#rfc.xref.header.location.4">10.3</a>, <a href="#rfc.xref.header.location.5">A</a></li> 3569 3573 <li>Max-Forwards <a href="#rfc.xref.header.max-forwards.1">3.2</a>, <a href="#rfc.xref.header.max-forwards.2">6.2</a>, <a href="#rfc.xref.header.max-forwards.3">6.8</a>, <a href="#rfc.iref.h.7"><b>9.6</b></a>, <a href="#rfc.xref.header.max-forwards.4">10.3</a>, <a href="#rfc.xref.header.max-forwards.5">A</a></li> 3570 3574 <li>Referer <a href="#rfc.xref.header.referer.1">3.2</a>, <a href="#rfc.iref.h.8"><b>9.7</b></a>, <a href="#rfc.xref.header.referer.2">10.3</a>, <a href="#rfc.xref.header.referer.3">A</a></li> … … 3581 3585 </li> 3582 3586 <li><a id="rfc.index.L" href="#rfc.index.L"><b>L</b></a><ul> 3583 <li>Location header field <a href="#rfc.xref.header.location.1">3.3</a>, <a href="#rfc.xref.header.location.2">6.5</a>, <a href="#rfc. iref.l.1"><b>9.5</b></a>, <a href="#rfc.xref.header.location.3">10.3</a>, <a href="#rfc.xref.header.location.4">A</a></li>3587 <li>Location header field <a href="#rfc.xref.header.location.1">3.3</a>, <a href="#rfc.xref.header.location.2">6.5</a>, <a href="#rfc.xref.header.location.3">7.3</a>, <a href="#rfc.iref.l.1"><b>9.5</b></a>, <a href="#rfc.xref.header.location.4">10.3</a>, <a href="#rfc.xref.header.location.5">A</a></li> 3584 3588 </ul> 3585 3589 </li>
Note: See TracChangeset
for help on using the changeset viewer.