Ignore:
Timestamp:
Dec 31, 2012, 3:02:54 AM (7 years ago)
Author:
fielding@…
Message:

fix several more cases of include being used instead of send or generate, and a few requirements that are simply facts

File:
1 edited

Legend:

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

    r2069 r2073  
    17831783  <iref primary="true" item="110 Response is Stale (warn code)" x:for-anchor=""/>
    17841784<t>
    1785    A cache &SHOULD; include this whenever the sent response is stale.
     1785   A cache &SHOULD; generate this whenever the sent response is stale.
    17861786</t>
    17871787</section>
     
    17901790  <iref primary="true" item="111 Revalidation Failed (warn code)" x:for-anchor=""/>
    17911791<t>
    1792    A cache &SHOULD; include this when sending a stale response because an
     1792   A cache &SHOULD; generate this when sending a stale response because an
    17931793   attempt to validate the response failed, due to an inability to reach
    17941794   the server.
     
    17991799  <iref primary="true" item="112 Disconnected Operation (warn code)" x:for-anchor=""/>
    18001800<t>
    1801    A cache &SHOULD; include this if it is intentionally disconnected from
     1801   A cache &SHOULD; generate this if it is intentionally disconnected from
    18021802   the rest of the network for a period of time.
    18031803</t>
     
    18071807  <iref primary="true" item="113 Heuristic Expiration (warn code)" x:for-anchor=""/>
    18081808<t>
    1809    A cache &SHOULD; include this if it heuristically chose a freshness
     1809   A cache &SHOULD; generate this if it heuristically chose a freshness
    18101810   lifetime greater than 24 hours and the response's age is greater than 24
    18111811   hours.
Note: See TracChangeset for help on using the changeset viewer.