Changeset 1498 for draft-ietf-httpbis/latest/p2-semantics.html

Timestamp:

Jan 1, 2012, 7:21:56 AM (8 years ago)

Author:

julian.reschke@…

Message:

Note that Location on 3xx indicates that the recipient MAY follow the redirect (see #325)

File:

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

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

@@ -1782 +1782 @@
          </p> 
       </div>
-      <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).
-      </p>
-      <div class="note" id="rfc.section.7.3.p.5"> 
+      <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&nbsp;9.5</a>.
+      </p>
+      <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).
+      </p>
+      <div class="note" id="rfc.section.7.3.p.6"> 
          <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.
          </p> 
@@ -2755 +2757 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.location" id="rfc.xref.header.location.3" title="Location">Section&nbsp;9.5</a> 
+                  <td class="left"> <a href="#header.location" id="rfc.xref.header.location.4" title="Location">Section&nbsp;9.5</a> 
                   </td>
                </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
          symbol "absoluteURI" wasn't what was expected, and add some clarifications as to when use of fragments would not be appropriate.
-         (<a href="#header.location" id="rfc.xref.header.location.4" title="Location">Section&nbsp;9.5</a>)
+         (<a href="#header.location" id="rfc.xref.header.location.5" title="Location">Section&nbsp;9.5</a>)
       </p>
       <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&nbsp;9.6</a>)
@@ -3420 +3422 @@
          </li>
          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/312">http://tools.ietf.org/wg/httpbis/trac/ticket/312</a>&gt;: "should there be a permanent variant of 307"
+         </li>
+         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/325">http://tools.ietf.org/wg/httpbis/trac/ticket/325</a>&gt;: "When are Location's semantics triggered?"
          </li>
          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/327">http://tools.ietf.org/wg/httpbis/trac/ticket/327</a>&gt;: "'expect' grammar missing OWS"
@@ -3566 +3570 @@
                         <li>Expect&nbsp;&nbsp;<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>
                         <li>From&nbsp;&nbsp;<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>
-                        <li>Location&nbsp;&nbsp;<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>
+                        <li>Location&nbsp;&nbsp;<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>
                         <li>Max-Forwards&nbsp;&nbsp;<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>
                         <li>Referer&nbsp;&nbsp;<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>
             <li><a id="rfc.index.L" href="#rfc.index.L"><b>L</b></a><ul>
-                  <li>Location header field&nbsp;&nbsp;<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>
+                  <li>Location header field&nbsp;&nbsp;<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>
                </ul>
             </li>