Changeset 697 for draft-ietf-httpbis/latest/p6-cache.html
- Timestamp:
- 25/09/09 14:43:16 (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.html
r694 r697 398 398 <meta name="DC.Creator" content="Reschke, J. F."> 399 399 <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest"> 400 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-09- 16">400 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-09-25"> 401 401 <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> 402 402 <meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. This document is Part 6 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages."> … … 430 430 </tr> 431 431 <tr> 432 <td class="header left">Expires: March 2 0, 2010</td>432 <td class="header left">Expires: March 29, 2010</td> 433 433 <td class="header right">HP</td> 434 434 </tr> … … 487 487 <tr> 488 488 <td class="header left"></td> 489 <td class="header right">September 16, 2009</td>489 <td class="header right">September 25, 2009</td> 490 490 </tr> 491 491 </table> … … 511 511 <p>The list of Internet-Draft Shadow Directories can be accessed at <<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>>. 512 512 </p> 513 <p>This Internet-Draft will expire in March 2 0, 2010.</p>513 <p>This Internet-Draft will expire in March 29, 2010.</p> 514 514 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 515 515 <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 974 974 <div id="rfc.iref.h.2"></div> 975 975 <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a> <a id="header.age" href="#header.age">Age</a></h2> 976 <p id="rfc.section.3.1.p.1">The response-header field "Age"conveys the sender's estimate of the amount of time since the response (or its validation)976 <p id="rfc.section.3.1.p.1">The "Age" response-header field conveys the sender's estimate of the amount of time since the response (or its validation) 977 977 was generated at the origin server. Age values are calculated as specified in <a href="#age.calculations" title="Calculating Age">Section 2.3.2</a>. 978 978 </p> … … 992 992 <div id="rfc.iref.h.3"></div> 993 993 <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a> <a id="header.cache-control" href="#header.cache-control">Cache-Control</a></h2> 994 <p id="rfc.section.3.2.p.1">The general-header field "Cache-Control"is used to specify directives that <em class="bcp14">MUST</em> be obeyed by all caches along the request/response chain. The directives specify behavior intended to prevent caches from994 <p id="rfc.section.3.2.p.1">The "Cache-Control" general-header field is used to specify directives that <em class="bcp14">MUST</em> be obeyed by all caches along the request/response chain. The directives specify behavior intended to prevent caches from 995 995 adversely interfering with the request or response. Cache directives are unidirectional in that the presence of a directive 996 996 in a request does not imply that the same directive is to be given in the response. … … 1195 1195 <div id="rfc.iref.h.4"></div> 1196 1196 <h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a> <a id="header.expires" href="#header.expires">Expires</a></h2> 1197 <p id="rfc.section.3.3.p.1">The entity-header field "Expires"gives the date/time after which the response is considered stale. See <a href="#expiration.model" title="Freshness Model">Section 2.3</a> for further discussion of the freshness model.1197 <p id="rfc.section.3.3.p.1">The "Expires" entity-header field gives the date/time after which the response is considered stale. See <a href="#expiration.model" title="Freshness Model">Section 2.3</a> for further discussion of the freshness model. 1198 1198 </p> 1199 1199 <p id="rfc.section.3.3.p.2">The presence of an Expires field does not imply that the original resource will change or cease to exist at, before, or after … … 1217 1217 <div id="rfc.iref.h.5"></div> 1218 1218 <h2 id="rfc.section.3.4"><a href="#rfc.section.3.4">3.4</a> <a id="header.pragma" href="#header.pragma">Pragma</a></h2> 1219 <p id="rfc.section.3.4.p.1">The general-header field "Pragma"is used to include implementation-specific directives that might apply to any recipient1219 <p id="rfc.section.3.4.p.1">The "Pragma" general-header field is used to include implementation-specific directives that might apply to any recipient 1220 1220 along the request/response chain. All pragma directives specify optional behavior from the viewpoint of the protocol; however, 1221 1221 some systems <em class="bcp14">MAY</em> require that behavior be consistent with the directives. … … 1261 1261 <div id="rfc.iref.h.7"></div> 1262 1262 <h2 id="rfc.section.3.6"><a href="#rfc.section.3.6">3.6</a> <a id="header.warning" href="#header.warning">Warning</a></h2> 1263 <p id="rfc.section.3.6.p.1">The general-header field "Warning"is used to carry additional information about the status or transformation of a message1263 <p id="rfc.section.3.6.p.1">The "Warning" general-header field is used to carry additional information about the status or transformation of a message 1264 1264 that might not be reflected in the message. This information is typically used to warn about possible incorrectness introduced 1265 1265 by caching operations or transformations applied to the entity body of the message.
Note: See TracChangeset
for help on using the changeset viewer.