Ignore:
Timestamp:
Jul 9, 2012, 4:49:50 PM (7 years ago)
Author:
mnot@…
Message:

most -> many when taking about numbers of implementations; we haven't counted.

File:
1 edited

Legend:

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

    r1751 r1752  
    444444   The default <x:dfn>cache key</x:dfn> consists of the request method and
    445445   target URI.  However, since HTTP caches in common use today are typically
    446    limited to caching responses to GET, most implementations simply decline
     446   limited to caching responses to GET, many implementations simply decline
    447447   other methods and use only the URI as the key.
    448448</t>
     
    499499</t>
    500500<t>
    501    Note that, in normal operation, most caches will not store a response that
     501   Note that, in normal operation, many caches will not store a response that
    502502   has neither a cache validator nor an explicit expiration time, as such
    503503   responses are not usually useful to store. However, caches are not
     
    14881488</t>
    14891489<t>
    1490    &Note; Most HTTP/1.0 caches will not recognize or obey
     1490   &Note; Many HTTP/1.0 caches will not recognize or obey
    14911491   this directive. Also, no-cache response directives with field-names are
    14921492   often handled by implementations as if an unqualified no-cache directive
     
    17391739   prohibited, extremely large values have been demonstrated to cause
    17401740   problems (e.g., clock overflows due to use of 32-bit integers for
    1741    time values), and most caches will evict a response far sooner than
     1741   time values), and many caches will evict a response far sooner than
    17421742   that. Therefore, senders ought not produce them.
    17431743</t>
Note: See TracChangeset for help on using the changeset viewer.