Ignore:
Timestamp:
May 2, 2012, 8:41:36 AM (8 years ago)
Author:
julian.reschke@…
Message:

update to latest version of rfc2629.xslt

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.html

    r1660 r1661  
    460460  }
    461461  @bottom-center {
    462        content: "Expires November 2, 2012";
     462       content: "Expires November 3, 2012";
    463463  }
    464464  @bottom-right {
     
    502502      <link href="p1-messaging.html" rel="prev">
    503503      <link href="p3-payload.html" rel="next">
    504       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.572, 2012-03-19 14:26:22, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     504      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.576, 2012-05-02 14:26:45, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    505505      <link rel="schema.dct" href="http://purl.org/dc/terms/">
    506506      <meta name="dct.creator" content="Fielding, R.">
     
    508508      <meta name="dct.creator" content="Reschke, J. F.">
    509509      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
    510       <meta name="dct.issued" scheme="ISO8601" content="2012-05-01">
     510      <meta name="dct.issued" scheme="ISO8601" content="2012-05-02">
    511511      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    512512      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request header fields, response status codes, and response header fields. Furthermore, it defines HTTP message content, metadata, and content negotiation. #351">
     
    539539            </tr>
    540540            <tr>
    541                <td class="left">Expires: November 2, 2012</td>
     541               <td class="left">Expires: November 3, 2012</td>
    542542               <td class="right">greenbytes</td>
    543543            </tr>
    544544            <tr>
    545545               <td class="left"></td>
    546                <td class="right">May 1, 2012</td>
     546               <td class="right">May 2, 2012</td>
    547547            </tr>
    548548         </tbody>
     
    574574         in progress”.
    575575      </p>
    576       <p>This Internet-Draft will expire on November 2, 2012.</p>
     576      <p>This Internet-Draft will expire on November 3, 2012.</p>
    577577      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    578578      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
Note: See TracChangeset for help on using the changeset viewer.