Jul 28, 2011, 2:01:10 PM (8 years ago)

remove mention of C-MD5 in HEAD (see #178)

1 edited


  • draft-ietf-httpbis/latest/p2-semantics.html

    r1364 r1367  
    359359  }
    360360  @bottom-center {
    361        content: "Expires January 28, 2012";
     361       content: "Expires January 29, 2012";
    362362  }
    363363  @bottom-right {
    409409      <meta name="dct.creator" content="Reschke, J. F.">
    410410      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
    411       <meta name="dct.issued" scheme="ISO8601" content="2011-07-27">
     411      <meta name="dct.issued" scheme="ISO8601" content="2011-07-28">
    412412      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    413413      <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 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.">
    440440            </tr>
    441441            <tr>
    442                <td class="left">Expires: January 28, 2012</td>
     442               <td class="left">Expires: January 29, 2012</td>
    443443               <td class="right">HP</td>
    444444            </tr>
    493493            <tr>
    494494               <td class="left"></td>
    495                <td class="right">July 27, 2011</td>
     495               <td class="right">July 28, 2011</td>
    496496            </tr>
    497497         </tbody>
    522522         in progress”.
    523523      </p>
    524       <p>This Internet-Draft will expire on January 28, 2012.</p>
     524      <p>This Internet-Draft will expire on January 29, 2012.</p>
    525525      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    526526      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    13601360      </p>
    13611361      <p id="rfc.section.7.4.p.2">The response to a HEAD request is cacheable and <em class="bcp14">MAY</em> be used to satisfy a subsequent HEAD request; see <a href="#Part6" id="rfc.xref.Part6.7"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>. It also <em class="bcp14">MAY</em> be used to update a previously cached representation from that resource; if the new field values indicate that the cached
    1362          representation differs from the current representation (as would be indicated by a change in Content-Length, Content-MD5,
    1363          ETag or Last-Modified), then the cache <em class="bcp14">MUST</em> treat the cache entry as stale.
     1362         representation differs from the current representation (as would be indicated by a change in Content-Length, ETag or Last-Modified),
     1363         then the cache <em class="bcp14">MUST</em> treat the cache entry as stale.
    13641364      </p>
    13651365      <p id="rfc.section.7.4.p.3">Bodies on HEAD requests have no defined semantics. Note that sending a body on a HEAD request might cause some existing implementations
Note: See TracChangeset for help on using the changeset viewer.