Changeset 444
- Timestamp:
- 03/02/09 11:03:36 (13 years ago)
- Location:
- draft-ietf-httpbis
- Files:
-
- 4 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest-roy/p6-cache.html
r442 r444 1189 1189 <div id="rfc.iref.h.4"></div> 1190 1190 <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> 1191 <p id="rfc.section.3.3.p.1">The Expires entity-header fieldgives 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 expiration model.1191 <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 expiration model. 1192 1192 </p> 1193 1193 <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 -
draft-ietf-httpbis/latest-roy/p6-cache.xml
r442 r444 1094 1094 <x:anchor-alias value="Expires"/> 1095 1095 <x:anchor-alias value="Expires-v"/> 1096 <t>The Expires entity-header fieldgives the date/time after which the response is1096 <t>The entity-header field "Expires" gives the date/time after which the response is 1097 1097 considered stale. See <xref target="expiration.model" /> for further discussion of the 1098 1098 expiration model.</t> -
draft-ietf-httpbis/latest/p6-cache.html
r443 r444 486 486 <tr> 487 487 <td class="header left"></td> 488 <td class="header right">February 2, 2009</td>488 <td class="header right">February 3, 2009</td> 489 489 </tr> 490 490 </table> … … 1572 1572 <div id="rfc.iref.h.4"></div> 1573 1573 <h2 id="rfc.section.15.3"><a href="#rfc.section.15.3">15.3</a> <a id="header.expires" href="#header.expires">Expires</a></h2> 1574 <p id="rfc.section.15.3.p.1">The Expires entity-header fieldgives the date/time after which the response is considered stale. A stale cache entry may1574 <p id="rfc.section.15.3.p.1">The entity-header field "Expires" gives the date/time after which the response is considered stale. A stale cache entry may 1575 1575 not normally be returned by a cache (either a proxy cache or a user agent cache) unless it is first validated with the origin 1576 1576 server (or with an intermediate cache that has a fresh copy of the entity). See <a href="#expiration.model" title="Expiration Model">Section 3</a> for further discussion of the expiration model. -
draft-ietf-httpbis/latest/p6-cache.xml
r443 r444 2111 2111 <x:anchor-alias value="Expires-v"/> 2112 2112 <t> 2113 The Expires entity-header fieldgives the date/time after which the2113 The entity-header field "Expires" gives the date/time after which the 2114 2114 response is considered stale. A stale cache entry may not normally be 2115 2115 returned by a cache (either a proxy cache or a user agent cache)
Note: See TracChangeset
for help on using the changeset viewer.