Changeset 1367 for draft-ietf-httpbis/latest/p2-semantics.html
- Timestamp:
- 28/07/11 21:01:10 (11 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r1364 r1367 359 359 } 360 360 @bottom-center { 361 content: "Expires January 2 8, 2012";361 content: "Expires January 29, 2012"; 362 362 } 363 363 @bottom-right { … … 409 409 <meta name="dct.creator" content="Reschke, J. F."> 410 410 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 411 <meta name="dct.issued" scheme="ISO8601" content="2011-07-2 7">411 <meta name="dct.issued" scheme="ISO8601" content="2011-07-28"> 412 412 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 413 413 <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 "HTTP/1.1" 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."> … … 440 440 </tr> 441 441 <tr> 442 <td class="left">Expires: January 2 8, 2012</td>442 <td class="left">Expires: January 29, 2012</td> 443 443 <td class="right">HP</td> 444 444 </tr> … … 493 493 <tr> 494 494 <td class="left"></td> 495 <td class="right">July 2 7, 2011</td>495 <td class="right">July 28, 2011</td> 496 496 </tr> 497 497 </tbody> … … 522 522 in progress”. 523 523 </p> 524 <p>This Internet-Draft will expire on January 2 8, 2012.</p>524 <p>This Internet-Draft will expire on January 29, 2012.</p> 525 525 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 526 526 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1360 1360 </p> 1361 1361 <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. 1364 1364 </p> 1365 1365 <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.