Ignore:
Timestamp:
Jan 22, 2008, 6:11:10 PM (12 years ago)
Author:
fielding@…
Message:

editorial: replace redundant "the HTTP protocol" phrases or rephrase

File:
1 edited

Legend:

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

    r170 r172  
    964964   retransmitting the full response if the cached entry is good, and we
    965965   do not want to pay the overhead of an extra round trip if the cached
    966    entry is invalid, the HTTP/1.1 protocol supports the use of
     966   entry is invalid, HTTP/1.1 supports the use of
    967967   conditional methods.
    968968</t>
     
    11411141<section title="Non-modifiable Headers" anchor="non-modifiable.headers">
    11421142<t>
    1143    Some features of the HTTP/1.1 protocol, such as Digest
     1143   Some features of HTTP/1.1, such as Digest
    11441144   Authentication, depend on the value of certain end-to-end headers. A
    11451145   transparent proxy &SHOULD-NOT;  modify an end-to-end header unless the
     
    13931393</t>
    13941394<t>
    1395    There is no way for the HTTP protocol to guarantee that all such
     1395   There is no way for HTTP to guarantee that all such
    13961396   cache entries are marked invalid. For example, the request that
    13971397   caused the change at the origin server might not have gone through
     
    16091609   the named field or fields, and not to the rest of the request or
    16101610   response. This mechanism supports extensibility; implementations of
    1611    future versions of the HTTP protocol might apply these directives to
     1611   future versions of HTTP might apply these directives to
    16121612   header fields not defined in HTTP/1.1.
    16131613</t>
Note: See TracChangeset for help on using the changeset viewer.