Ignore:
Timestamp:
Jun 20, 2008, 9:48:20 AM (11 years ago)
Author:
julian.reschke@…
Message:

Resolve #121: RFC 2183 replaced RFC 1806, only cite the newer one (closes #121).

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p3-payload.xml

    r268 r269  
    16241624<section title="Content-Disposition Issues" anchor="content-disposition.issues">
    16251625<t>
    1626    <xref target="RFC1806"/>, from which the often implemented Content-Disposition
     1626   <xref target="RFC2183"/>, from which the often implemented Content-Disposition
    16271627   (see <xref target="content-disposition"/>) header in HTTP is derived, has a number of very
    16281628   serious security considerations. Content-Disposition is not part of
    16291629   the HTTP standard, but since it is widely implemented, we are
    1630    documenting its use and risks for implementors. See <xref target="RFC2183"/>
    1631    (which updates <xref target="RFC1806"/>) for details.
     1630   documenting its use and risks for implementors. See <xref target="RFC2183" x:fmt="of" x:sec="5"/>
     1631   for details.
    16321632</t>
    16331633</section>
     
    20302030<references title="Informative References">
    20312031
    2032 <reference anchor="RFC1806">
    2033   <front>
    2034     <title abbrev="Content-Disposition">Communicating Presentation Information in Internet Messages: The Content-Disposition Header</title>
    2035     <author initials="R." surname="Troost" fullname="Rens Troost">
    2036       <organization>New Century Systems</organization>
    2037       <address><email>rens@century.com</email></address>
    2038     </author>
    2039     <author initials="S." surname="Dorner" fullname="Steve Dorner">
    2040       <organization>QUALCOMM Incorporated</organization>
    2041       <address><email>sdorner@qualcomm.com</email></address>
    2042     </author>
    2043     <date month="June" year="1995"/>
    2044   </front>
    2045   <seriesInfo name="RFC" value="1806"/>
    2046 </reference>
    2047 
    20482032<reference anchor="RFC1945">
    20492033  <front>
     
    24502434   means for the origin server to suggest a default filename if the user
    24512435   requests that the content is saved to a file. This usage is derived
    2452    from the definition of Content-Disposition in <xref target="RFC1806"/>.
     2436   from the definition of Content-Disposition in <xref target="RFC2183"/>.
    24532437</t>
    24542438<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="content-disposition"/><iref primary="true" item="Grammar" subitem="disposition-type"/><iref primary="true" item="Grammar" subitem="disposition-parm"/><iref primary="true" item="Grammar" subitem="filename-parm"/><iref primary="true" item="Grammar" subitem="disp-extension-token"/><iref primary="true" item="Grammar" subitem="disp-extension-parm"/>
     
    26382622<section title="Since draft-ietf-httpbis-p3-payload-03" anchor="changes.since.03">
    26392623<t>
    2640 </t>
    2641 </section>
     2624  Closed issues:
     2625  <list style="symbols">
     2626    <t>
     2627      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/121"/>:
     2628      "RFC 1806 has been replaced by RFC2183"
     2629    </t>
     2630  </list>
     2631</t>
     2632 </section>
    26422633
    26432634</section>
Note: See TracChangeset for help on using the changeset viewer.