Changeset 528 for draft-ietf-httpbis
- Timestamp:
- 05/03/09 06:27:23 (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest-roy/p6-cache.xml
r527 r528 1030 1030 <t>The Cache-Control header field can be extended through the use of one or more 1031 1031 cache-extension tokens, each with an optional value. Informational extensions (those 1032 whichdo not require a change in cache behavior) &MAY; be added without changing the1032 that do not require a change in cache behavior) &MAY; be added without changing the 1033 1033 semantics of other directives. Behavioral extensions are designed to work by acting as 1034 1034 modifiers to the existing base of cache directives. Both the new directive and the 1035 standard directive are supplied, such that applications whichdo not understand the new1035 standard directive are supplied, such that applications that do not understand the new 1036 1036 directive will default to the behavior specified by the standard directive, and those 1037 1037 that understand the new directive will recognize it as modifying the requirements … … 1041 1041 directives defined for its native HTTP-version, obeying certain extensions, and ignoring 1042 1042 all directives that it does not understand.</t> 1043 <t>For example, consider a hypothetical new response directive called "community" which1043 <t>For example, consider a hypothetical new response directive called "community" that 1044 1044 acts as a modifier to the private directive. We define this new directive to mean that, 1045 in addition to any non-shared cache, any cache whichis shared only by members of the1045 in addition to any non-shared cache, any cache that is shared only by members of the 1046 1046 community named within its value may cache the response. An origin server wishing to 1047 1047 allow the UCI community to use an otherwise private response in their shared cache(s) … … 1177 1177 <x:anchor-alias value="warn-text"/> 1178 1178 <t>The general-header field "Warning" is used to carry additional information about the status 1179 or transformation of a message whichmight not be reflected in the message. This1179 or transformation of a message that might not be reflected in the message. This 1180 1180 information is typically used to warn about possible incorrectness introduced by caching 1181 1181 operations or transformations applied to the entity body of the message.</t> … … 1226 1226 <t>2xx Warnings that describe some aspect of the entity body or entity headers that is 1227 1227 not rectified by a validation (for example, a lossy compression of the entity bodies) 1228 and which&MUST-NOT; be deleted by caches after validation, unless a full response is1228 and &MUST-NOT; be deleted by caches after validation, unless a full response is 1229 1229 returned, in which case they &MUST; be.</t> 1230 1230 </list> … … 1293 1293 1294 1294 <section anchor="history.lists" title="History Lists"> 1295 <t>User agents often have history mechanisms, such as "Back" buttons and history lists, which1295 <t>User agents often have history mechanisms, such as "Back" buttons and history lists, that 1296 1296 can be used to redisplay an entity retrieved earlier in a session.</t> 1297 1297 <t>History mechanisms and caches are different. In particular history mechanisms
Note: See TracChangeset
for help on using the changeset viewer.