Ignore:
Timestamp:
Jun 1, 2011, 2:03:44 AM (9 years ago)
Author:
julian.reschke@…
Message:

update rfc2629.xslt, bump up document dates

File:
1 edited

Legend:

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

    r1299 r1303  
    325325  }
    326326  @bottom-center {
    327        content: "Expires November 28, 2011";
     327       content: "Expires November 2011";
    328328  }
    329329  @bottom-right {
     
    361361      <link rel="Appendix" title="C Alternative Approaches to Internationalization" href="#rfc.section.C">
    362362      <link rel="Appendix" title="D Advice on Generating Content-Disposition Header Fields" href="#rfc.section.D">
    363       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.547, 2011-04-17 09:42:41, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     363      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.550, 2011-05-30 14:02:12, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    364364      <meta name="keywords" content="HTTP, Hypertext Transfer Protocol, Content-Disposition, filename, attachment, inline">
    365365      <link rel="schema.dct" href="http://purl.org/dc/terms/">
    366366      <meta name="dct.creator" content="Reschke, J. F.">
    367367      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-content-disp-latest">
    368       <meta name="dct.issued" scheme="ISO8601" content="2011-05-27">
     368      <meta name="dct.issued" scheme="ISO8601" content="2011-05">
    369369      <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.">
    370370      <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.">
     
    384384               <td class="left">Updates: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved)
    385385               </td>
    386                <td class="right">May 27, 2011</td>
     386               <td class="right">May 2011</td>
    387387            </tr>
    388388            <tr>
     
    391391            </tr>
    392392            <tr>
    393                <td class="left">Expires: November 28, 2011</td>
     393               <td class="left">Expires: November 2011</td>
    394394               <td class="right"></td>
    395395            </tr>
     
    411411         in progress”.
    412412      </p>
    413       <p>This Internet-Draft will expire on November 28, 2011.</p>
     413      <p>This Internet-Draft will expire in November 2011.</p>
    414414      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    415415      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
Note: See TracChangeset for help on using the changeset viewer.