Ignore:
Timestamp:
May 8, 2013, 6:06:21 AM (6 years ago)
Author:
mnot@…
Message:

Address editorial feedback from Alex; see #480

File:
1 edited

Legend:

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

    r2246 r2247  
    204204</artwork></figure>
    205205<t>
    206    If an implementation receives a delta-seconds value larger than the largest
     206   If a cache receives a delta-seconds value larger than the largest
    207207   positive integer it can represent, or if any of its subsequent calculations
    208208   overflows, it &MUST; consider the value to be 2147483648
    209209   (2<x:sup>31</x:sup>). Recipients parsing a delta-seconds value &MUST; use
    210210   an arithmetic type of at least 31 bits of range, and senders &MUST-NOT;
    211    send delta-seconds with a value greater than 2147483648.
     211   generate delta-seconds with a value greater than 2147483648.
    212212</t>
    213213</section>
     
    246246   The primary <x:dfn>cache key</x:dfn> consists of the request method and
    247247   target URI.  However, since HTTP caches in common use today are typically
    248    limited to caching responses to GET, many implementations simply decline
     248   limited to caching responses to GET, many caches simply decline
    249249   other methods and use only the URI as the primary cache key.
    250250</t>
     
    736736</t>
    737737<t>
    738    A cache &MUST-NOT; send a stale response if it is prohibited by an
     738   A cache &MUST-NOT; generate a stale response if it is prohibited by an
    739739   explicit in-protocol directive (e.g., by a "no-store" or "no-cache" cache
    740740   directive, a "must-revalidate" cache-response-directive, or an applicable
     
    760760   an entire response, or a <x:ref>304 (Not Modified)</x:ref> response) that
    761761   it would normally forward to the requesting client, and the received
    762    response is no longer fresh, the cache can forward it to the requesting
     762   response is no longer fresh, the cache &MAY; forward it to the requesting
    763763   client without adding a new <x:ref>Warning</x:ref> (but without removing
    764764   any existing Warning header fields). A cache shouldn't attempt to validate
     
    845845     &weak-and-strong;), then that strong validator identifies the selected
    846846     representation for update. All of the stored responses with the same
    847      strong validator are selected. If none of the stored responses contain
    848      the same strong validator, then the new response &MUST-NOT; be used to
     847     strong validator are selected. If none of the stored responses contain the
     848     same strong validator, then the cache &MUST-NOT; use the new response to
    849849     update any stored responses.
    850850    </t>
     
    12831283   &Note; Although it has been back-ported to many implementations, some
    12841284   HTTP/1.0 caches will not recognize or obey this directive. Also, no-cache
    1285    response directives with field-names are often handled by implementations
     1285   response directives with field-names are often handled by caches
    12861286   as if an unqualified no-cache directive was received; i.e., the special
    12871287   handling for the qualified form is not widely implemented.
     
    13671367   where the response can be stored; it cannot ensure the privacy of the
    13681368   message content. Also, private response directives with field-names are
    1369    often handled by implementations as if an unqualified private directive
     1369   often handled by caches as if an unqualified private directive
    13701370   was received; i.e., the special handling for the qualified form is not
    13711371   widely implemented.
     
    15791579<t>
    15801580   When the <x:ref>Cache-Control</x:ref> header field is not present in a
    1581    request, the no-cache request pragma-directive &MUST; have the same effect
    1582    on caches as if "Cache-Control: no-cache" were present (see <xref
    1583    target="cache-request-directive" />).
     1581   request, caches &MUST; consider the no-cache request pragma-directive as
     1582   having the same effect as if "Cache-Control: no-cache" were present (see
     1583   <xref target="cache-request-directive" />).
    15841584</t>
    15851585<t>
Note: See TracChangeset for help on using the changeset viewer.