Changeset 629

Timestamp:

27/07/09 15:15:31 (12 years ago)

Author:

julian.reschke@…

Message:

Resolve #182: rephrase a note so it becomes clear it refers to RFC 2068, not RFC 2616 (closes #182)

Location:

draft-ietf-httpbis/latest

Files:

• p2-semantics.html (modified) (5 diffs)
• p2-semantics.xml (modified) (2 diffs)

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

@@ -1169 +1169 @@
       </p>
       <div class="note"> 
-         <p> <b>Note:</b> previous versions of this specification recommended a maximum of five redirections. Content developers should be aware that
-            there might be clients that implement such a fixed limitation.
+         <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.
          </p> 
       </div>
@@ -1215 +1214 @@
       </p>
       <div class="note"> 
-         <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 agent
+         <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
             implementations treat 302 as if it were a 303 response, performing a GET on the Location field-value regardless of the original
             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&nbsp;8.3.4</a>) and 307 (<a href="#status.307" id="rfc.xref.status.307.2" title="307 Temporary Redirect">Section&nbsp;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>)
       </p>
-      <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>.
+      <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>.
       </p>
       <h2 id="rfc.section.A.2"><a href="#rfc.section.A.2">A.2</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
@@ -2503 +2502 @@
       <ul>
          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/140">http://tools.ietf.org/wg/httpbis/trac/ticket/140</a>&gt;: "update note citing RFC 1945 and 2068"
+         </li>
+         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/182">http://tools.ietf.org/wg/httpbis/trac/ticket/182</a>&gt;: "update note about redirect limit"
          </li>
       </ul>
@@ -2735 +2736 @@
                      </ul>
                   </li>
-                  <li class="indline1"><em>RFC2068</em>&nbsp;&nbsp;<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">
-                        <li class="indline1"><em>Section 10.3.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2068.1">8.3.3</a></li>
-                        <li class="indline1"><em>Section 19.6.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2068.2">A.1</a></li>
+                  <li class="indline1"><em>RFC2068</em>&nbsp;&nbsp;<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">
+                        <li class="indline1"><em>Section 10.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2068.1">8.3</a></li>
+                        <li class="indline1"><em>Section 10.3.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2068.2">8.3.3</a></li>
+                        <li class="indline1"><em>Section 19.6.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2068.3">A.1</a></li>
                      </ul>
                   </li>

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

@@ -1242 +1242 @@
 <x:note>
   <t>
-    <x:h>Note:</x:h> previous versions of this specification recommended a
-    maximum of five redirections. Content developers should be aware
-    that there might be clients that implement such a fixed
-    limitation.
+    <x:h>Note:</x:h> an earlier version of this specification recommended a
+    maximum of five redirections (<xref target="RFC2068" x:fmt="," x:sec="10.3"/>).
+    Content developers should be aware that there might be clients that
+    implement such a fixed limitation.
   </t>
 </x:note>
@@ -3622 +3622 @@
       "update note citing RFC 1945 and 2068"
     </t>
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/182"/>:
+      "update note about redirect limit"
+    </t>
   </list>
 </t>