Ignore:
Timestamp:
Mar 10, 2011, 9:42:12 PM (9 years ago)
Author:
fielding@…
Message:

update generated HTML

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p3-payload.html

    r1154 r1162  
    359359  }
    360360  @bottom-center {
    361        content: "Expires September 10, 2011";
     361       content: "Expires September 11, 2011";
    362362  }
    363363  @bottom-right {
     
    408408      <meta name="dct.creator" content="Reschke, J. F.">
    409409      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p3-payload-latest">
    410       <meta name="dct.issued" scheme="ISO8601" content="2011-03-09">
     410      <meta name="dct.issued" scheme="ISO8601" content="2011-03-10">
    411411      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    412412      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 3 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 3 defines HTTP message content, metadata, and content negotiation.">
     
    434434            </tr>
    435435            <tr>
    436                <td class="left">Expires: September 10, 2011</td>
     436               <td class="left">Expires: September 11, 2011</td>
    437437               <td class="right">J. Mogul</td>
    438438            </tr>
     
    491491            <tr>
    492492               <td class="left"></td>
    493                <td class="right">March 9, 2011</td>
     493               <td class="right">March 10, 2011</td>
    494494            </tr>
    495495         </tbody>
     
    517517         in progress”.
    518518      </p>
    519       <p>This Internet-Draft will expire on September 10, 2011.</p>
     519      <p>This Internet-Draft will expire on September 11, 2011.</p>
    520520      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    521521      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    13291329      <p id="rfc.section.6.7.p.4">If Content-Location is included in a response message and its value is the same as the effective request URI, then the response
    13301330         payload <em class="bcp14">SHOULD</em> be considered the current representation of that resource. For a GET or HEAD request, this is the same as the default semantics
    1331          when no Content-Location is provided by the server. For a state-changing method like PUT or POST, it implies that the server's
     1331         when no Content-Location is provided by the server. For a state-changing request like PUT or POST, it implies that the server's
    13321332         response contains the new representation of that resource, thereby distinguishing it from representations that might only
    13331333         report about the action (e.g., "It worked!"). This allows authoring applications to update their local copies without the
     
    13391339         and the representation selected for this response can also be found at the identified URI. For other methods, such a Content-Location
    13401340         indicates that this representation contains a report on the action's status and the same report is available (for future access
    1341          with GET) at the given URI. For example, a purchase transaction made via the POST method might include a receipt document
    1342          as the payload of the 200 response; the Content-Location value provides an identifier for retrieving a copy of that same receipt
     1341         with GET) at the given URI. For example, a purchase transaction made via a POST request might include a receipt document as
     1342         the payload of the 200 response; the Content-Location value provides an identifier for retrieving a copy of that same receipt
    13431343         in the future.
    13441344      </p>
Note: See TracChangeset for help on using the changeset viewer.