Ignore:
Timestamp:
May 1, 2011, 2:08:45 AM (9 years ago)
Author:
julian.reschke@…
Message:

bump up document dates, latest version of rfc2629.xslt

Location:
draft-ietf-httpbis-content-disp/latest
Files:
2 edited

Legend:

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

    r1254 r1276  
    362362  }
    363363  @top-right {
    364        content: "April 2011";
     364       content: "May 2011";
    365365  }
    366366  @top-center {
     
    371371  }
    372372  @bottom-center {
    373        content: "Expires October 3, 2011";
     373       content: "Expires November 2, 2011";
    374374  }
    375375  @bottom-right {
     
    408408      <link rel="Appendix" title="D Advice on Generating Content-Disposition Header Fields" href="#rfc.section.D">
    409409      <link rel="Appendix" title="E Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.E">
    410       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.543, 2011-02-18 21:03:40, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     410      <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/">
    411411      <link rel="schema.dct" href="http://purl.org/dc/terms/">
    412412      <meta name="dct.creator" content="Reschke, J. F.">
    413413      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-content-disp-latest">
    414       <meta name="dct.issued" scheme="ISO8601" content="2011-04-01">
     414      <meta name="dct.issued" scheme="ISO8601" content="2011-05-01">
    415415      <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.">
    416416      <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.">
     
    430430               <td class="left">Updates: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved)
    431431               </td>
    432                <td class="right">April 1, 2011</td>
     432               <td class="right">May 1, 2011</td>
    433433            </tr>
    434434            <tr>
     
    437437            </tr>
    438438            <tr>
    439                <td class="left">Expires: October 3, 2011</td>
     439               <td class="left">Expires: November 2, 2011</td>
    440440               <td class="right"></td>
    441441            </tr>
     
    466466         in progress”.
    467467      </p>
    468       <p>This Internet-Draft will expire on October 3, 2011.</p>
     468      <p>This Internet-Draft will expire on November 2, 2011.</p>
    469469      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    470470      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
  • draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.xml

    r1254 r1276  
    4242  </author>
    4343
    44   <date month="April" year="2011"/>
     44  <date month="May" year="2011"/>
    4545  <workgroup>HTTPbis Working Group</workgroup>
    4646 
Note: See TracChangeset for help on using the changeset viewer.