Mar 13, 2011, 12:18:50 AM (9 years ago)

editorial: remove inappropriate implementation details from
the definition of last-modified.

1 edited


  • draft-ietf-httpbis/latest/p4-conditional.html

    r1165 r1172  
    359359  }
    360360  @bottom-center {
    361        content: "Expires September 12, 2011";
     361       content: "Expires September 14, 2011";
    362362  }
    363363  @bottom-right {
    406406      <meta name="dct.creator" content="Reschke, J. F.">
    407407      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest">
    408       <meta name="dct.issued" scheme="ISO8601" content="2011-03-11">
     408      <meta name="dct.issued" scheme="ISO8601" content="2011-03-13">
    409409      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    410410      <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 4 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 4 defines request header fields for indicating conditional requests and the rules for constructing responses to those requests.">
    432432            </tr>
    433433            <tr>
    434                <td class="left">Expires: September 12, 2011</td>
     434               <td class="left">Expires: September 14, 2011</td>
    435435               <td class="right">J. Mogul</td>
    436436            </tr>
    489489            <tr>
    490490               <td class="left"></td>
    491                <td class="right">March 11, 2011</td>
     491               <td class="right">March 13, 2011</td>
    492492            </tr>
    493493         </tbody>
    515515         in progress”.
    516516      </p>
    517       <p>This Internet-Draft will expire on September 12, 2011.</p>
     517      <p>This Internet-Draft will expire on September 14, 2011.</p>
    518518      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    519519      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    10741074</pre><p id="rfc.section.6.6.p.3">An example of its use is</p>
    10751075      <div id="rfc.figure.u.18"></div><pre class="text">  Last-Modified: Tue, 15 Nov 1994 12:45:26 GMT
    1076 </pre><p id="rfc.section.6.6.p.5">The exact meaning of this header field depends on the implementation of the origin server and the nature of the original resource.
    1077          For files, it might be just the file system last-modified time. For representations with dynamically included parts, it might
    1078          be the most recent of the set of last-modify times for its component parts. For database gateways, it might be the last-update
    1079          time stamp of the record. For virtual objects, it might be the last time the internal state changed.
     1076</pre><p id="rfc.section.6.6.p.5">A representation is typically the sum of many parts behind the resource interface. The last-modified time would usually be
     1077         the most recent time that any of those parts were changed. How that value is determined for any given resource is an implementation
     1078         detail beyond the scope of this specification. What matters to HTTP is how recipients of the Last-Modified header field can
     1079         use its value to make conditional requests and test the validity of locally cached responses.
    10801080      </p>
    10811081      <p id="rfc.section.6.6.p.6">An origin server <em class="bcp14">MUST NOT</em> send a Last-Modified date which is later than the server's time of message origination. In such cases, where the resource's
Note: See TracChangeset for help on using the changeset viewer.