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)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • 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.