Changeset 528


Ignore:
Timestamp:
Mar 4, 2009, 10:27:23 PM (11 years ago)
Author:
mnot@…
Message:

which hunt

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest-roy/p6-cache.xml

    r527 r528  
    10301030          <t>The Cache-Control header field can be extended through the use of one or more
    10311031            cache-extension tokens, each with an optional value. Informational extensions (those
    1032             which do not require a change in cache behavior) &MAY; be added without changing the
     1032            that do not require a change in cache behavior) &MAY; be added without changing the
    10331033            semantics of other directives. Behavioral extensions are designed to work by acting as
    10341034            modifiers to the existing base of cache directives. Both the new directive and the
    1035             standard directive are supplied, such that applications which do not understand the new
     1035            standard directive are supplied, such that applications that do not understand the new
    10361036            directive will default to the behavior specified by the standard directive, and those
    10371037            that understand the new directive will recognize it as modifying the requirements
     
    10411041            directives defined for its native HTTP-version, obeying certain extensions, and ignoring
    10421042            all directives that it does not understand.</t>
    1043           <t>For example, consider a hypothetical new response directive called "community" which
     1043          <t>For example, consider a hypothetical new response directive called "community" that
    10441044            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 which is shared only by members of the
     1045            in addition to any non-shared cache, any cache that is shared only by members of the
    10461046            community named within its value may cache the response. An origin server wishing to
    10471047            allow the UCI community to use an otherwise private response in their shared cache(s)
     
    11771177        <x:anchor-alias value="warn-text"/>
    11781178        <t>The general-header field "Warning" is used to carry additional information about the status
    1179           or transformation of a message which might not be reflected in the message. This
     1179          or transformation of a message that might not be reflected in the message. This
    11801180          information is typically used to warn about possible incorrectness introduced by caching
    11811181          operations or transformations applied to the entity body of the message.</t>
     
    12261226            <t>2xx Warnings that describe some aspect of the entity body or entity headers that is
    12271227              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 is
     1228              and &MUST-NOT; be deleted by caches after validation, unless a full response is
    12291229              returned, in which case they &MUST; be.</t>
    12301230          </list>
     
    12931293
    12941294    <section anchor="history.lists" title="History Lists">
    1295       <t>User agents often have history mechanisms, such as "Back" buttons and history lists, which
     1295      <t>User agents often have history mechanisms, such as "Back" buttons and history lists, that
    12961296        can be used to redisplay an entity retrieved earlier in a session.</t>
    12971297      <t>History mechanisms and caches are different. In particular history mechanisms
Note: See TracChangeset for help on using the changeset viewer.