Ignore:
Timestamp:
Feb 21, 2011, 1:52:17 AM (8 years ago)
Author:
julian.reschke@…
Message:

When the intro talks about HTTP/1.1 in some cases it really needs to say RFC 2616 (fixed)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.xml

    r1122 r1131  
    4747  <abstract>
    4848    <t>
    49       HTTP/1.1 defines the Content-Disposition response header field,
     49      RFC 2616 defines the Content-Disposition response header field,
    5050      but points out that it is not part of the HTTP/1.1 Standard.
    5151      This specification takes over the definition and registration of
     
    7878<section title="Introduction" anchor="introduction">
    7979<t>
    80   HTTP/1.1 defines the Content-Disposition response header field in <xref target="RFC2616" x:fmt="of" x:sec="19.5.1"/>,
     80  RFC 2616 defines the Content-Disposition response header field in <xref target="RFC2616" x:fmt="of" x:sec="19.5.1"/>,
    8181  but points out that it is not part of the HTTP/1.1 Standard (<xref target="RFC2616" x:fmt="sec" x:sec="15.5"/>):
    8282</t>
Note: See TracChangeset for help on using the changeset viewer.