Ignore:
Timestamp:
Dec 7, 2009, 9:46:53 AM (10 years ago)
Author:
julian.reschke@…
Message:

typos fixed (editorial change)

File:
1 edited

Legend:

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

    r729 r732  
    495495<t>
    496496  Requests with methods that are unsafe (&safe-methods;) &MUST; be written through the cache to
    497   the origin server; i.e., A cache must not reply to such a request before having forwarded the request and having received a
     497  the origin server; i.e., a cache must not reply to such a request before having forwarded the request and having received a
    498498  corresponding response.
    499499</t>
     
    11041104      be stored, and cannot ensure the privacy of the message content.
    11051105      Also, private response directives with field-names are often handled by
    1106       implementations as if an unqualified private directive was recieved; i.e.,
     1106      implementations as if an unqualified private directive was received; i.e.,
    11071107      the special handling for the qualified form is not widely implemented.
    11081108</t>
     
    13451345<t>
    13461346  Caches use this information, in part, to determine whether a stored response
    1347   can be used to satisdy a given request; see
     1347  can be used to satisfy a given request; see
    13481348  <xref target="caching.negotiated.responses" />.
    13491349  determines, while the response is fresh, whether a cache is permitted to use the
     
    14031403<t>
    14041404  Warnings can be used for other purposes, both cache-related and otherwise. The use of a
    1405   warning, rather than an error status code, distinguish these responses from true failures.
     1405  warning, rather than an error status code, distinguishes these responses from true failures.
    14061406</t>
    14071407<t>
Note: See TracChangeset for help on using the changeset viewer.