Ignore:
Timestamp:
Jul 9, 2012, 5:36:45 PM (7 years ago)
Author:
mnot@…
Message:

remove 'safe' from caching overview, as we don't restrict caching to safe methods

File:
1 edited

Legend:

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

    r1753 r1754  
    839839         negative results (e.g., <a href="p2-semantics.html#status.404" class="smpl">404 (Not
    840840            Found)</a>, incomplete results (e.g., <a href="p5-range.html#status.206" class="smpl">206 (Partial
    841             Content)</a>), and responses to safe methods other than GET if the method's definition allows such caching and defines something suitable
    842          for use as a cache key.
     841            Content)</a>), and responses to methods other than GET if the method's definition allows such caching and defines something suitable for
     842         use as a cache key.
    843843      </p>
    844844      <p id="rfc.section.2.p.3">The default <dfn>cache key</dfn> consists of the request method and target URI. However, since HTTP caches in common use today are typically limited to caching
Note: See TracChangeset for help on using the changeset viewer.