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.html

    r1122 r1131  
    365365  }
    366366  @bottom-center {
    367        content: "Expires August 21, 2011";
     367       content: "Expires August 25, 2011";
    368368  }
    369369  @bottom-right {
    … …  
    405405      <meta name="dct.creator" content="Reschke, J. F.">
    406406      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-content-disp-latest">
    407       <meta name="dct.issued" scheme="ISO8601" content="2011-02-17">
    408       <meta name="dct.abstract" content="HTTP/1.1 defines the Content-Disposition response header field, but points out that it is not part of the HTTP/1.1 Standard. This specification takes over the definition and registration of Content-Disposition, as used in HTTP, and clarifies internationalization aspects.">
    409       <meta name="description" content="HTTP/1.1 defines the Content-Disposition response header field, but points out that it is not part of the HTTP/1.1 Standard. This specification takes over the definition and registration of Content-Disposition, as used in HTTP, and clarifies internationalization aspects.">
     407      <meta name="dct.issued" scheme="ISO8601" content="2011-02-21">
     408      <meta name="dct.abstract" content="RFC 2616 defines the Content-Disposition response header field, but points out that it is not part of the HTTP/1.1 Standard. This specification takes over the definition and registration of Content-Disposition, as used in HTTP, and clarifies internationalization aspects.">
     409      <meta name="description" content="RFC 2616 defines the Content-Disposition response header field, but points out that it is not part of the HTTP/1.1 Standard. This specification takes over the definition and registration of Content-Disposition, as used in HTTP, and clarifies internationalization aspects.">
    410410   </head>
    411411   <body>
    … …  
    423423               <td class="left">Updates: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved)
    424424               </td>
    425                <td class="right">February 17, 2011</td>
     425               <td class="right">February 21, 2011</td>
    426426            </tr>
    427427            <tr>
    … …  
    430430            </tr>
    431431            <tr>
    432                <td class="left">Expires: August 21, 2011</td>
     432               <td class="left">Expires: August 25, 2011</td>
    433433               <td class="right"></td>
    434434            </tr>
    … …  
    437437      <p class="title">Use of the Content-Disposition&nbsp;Header&nbsp;Field in the Hypertext&nbsp;Transfer&nbsp;Protocol&nbsp;(HTTP)<br><span class="filename">draft-ietf-httpbis-content-disp-latest</span></p>
    438438      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
    439       <p>HTTP/1.1 defines the Content-Disposition response header field, but points out that it is not part of the HTTP/1.1 Standard.
     439      <p>RFC 2616 defines the Content-Disposition response header field, but points out that it is not part of the HTTP/1.1 Standard.
    440440         This specification takes over the definition and registration of Content-Disposition, as used in HTTP, and clarifies internationalization
    441441         aspects.
    … …  
    459459         in progress”.
    460460      </p>
    461       <p>This Internet-Draft will expire on August 21, 2011.</p>
     461      <p>This Internet-Draft will expire on August 25, 2011.</p>
    462462      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    463463      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    … …  
    521521      </ul>
    522522      <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
    523       <p id="rfc.section.1.p.1">HTTP/1.1 defines the Content-Disposition response header field in <a href="http://tools.ietf.org/html/rfc2616#section-19.5.1">Section 19.5.1</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, but points out that it is not part of the HTTP/1.1 Standard (<a href="http://tools.ietf.org/html/rfc2616#section-15.5" id="rfc.xref.RFC2616.2">Section 15.5</a>):
     523      <p id="rfc.section.1.p.1">RFC 2616 defines the Content-Disposition response header field in <a href="http://tools.ietf.org/html/rfc2616#section-19.5.1">Section 19.5.1</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, but points out that it is not part of the HTTP/1.1 Standard (<a href="http://tools.ietf.org/html/rfc2616#section-15.5" id="rfc.xref.RFC2616.2">Section 15.5</a>):
    524524      </p>
    525525      <blockquote id="rfc.section.1.p.2" cite="http://tools.ietf.org/html/rfc2616#section-15.5">
Note: See TracChangeset for help on using the changeset viewer.