Changeset 629 for draft-ietf-httpbis


Ignore:
Timestamp:
Jul 27, 2009, 8:15:31 AM (10 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:
2 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.html

    r628 r629  
    11691169      </p>
    11701170      <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.
    11731172         </p>
    11741173      </div>
     
    12151214      </p>
    12161215      <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 agent
     1216         <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
    12181217            implementations treat 302 as if it were a 303 response, performing a GET on the Location field-value regardless of the original
    12191218            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.
     
    22322231      <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>)
    22332232      </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>.
    22352234      </p>
    22362235      <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>
     
    25032502      <ul>
    25042503         <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"
     2504         </li>
     2505         <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"
    25052506         </li>
    25062507      </ul>
     
    27352736                     </ul>
    27362737                  </li>
    2737                   <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">
    2738                         <li class="indline1"><em>Section 10.3.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2068.1">8.3.3</a></li>
    2739                         <li class="indline1"><em>Section 19.6.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2068.2">A.1</a></li>
     2738                  <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">
     2739                        <li class="indline1"><em>Section 10.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2068.1">8.3</a></li>
     2740                        <li class="indline1"><em>Section 10.3.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2068.2">8.3.3</a></li>
     2741                        <li class="indline1"><em>Section 19.6.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2068.3">A.1</a></li>
    27402742                     </ul>
    27412743                  </li>
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r628 r629  
    12421242<x:note>
    12431243  <t>
    1244     <x:h>Note:</x:h> previous versions of this specification recommended a
    1245     maximum of five redirections. Content developers should be aware
    1246     that there might be clients that implement such a fixed
    1247     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.
    12481248  </t>
    12491249</x:note>
     
    36223622      "update note citing RFC 1945 and 2068"
    36233623    </t>
     3624    <t>
     3625      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/182"/>:
     3626      "update note about redirect limit"
     3627    </t>
    36243628  </list>
    36253629</t>
Note: See TracChangeset for help on using the changeset viewer.