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

(editorial) that vs which

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r2072 r2074  
    575575   applicable to that request. The following illustrates the resulting
    576576   chain if B has a cached copy of an earlier response from O (via C)
    577    for a request which has not been cached by UA or A.
     577   for a request that has not been cached by UA or A.
    578578</t>
    579579<figure><artwork type="drawing">
     
    25962596   Senders &SHOULD-NOT; combine multiple entries unless they are all
    25972597   under the same organizational control and the hosts have already been
    2598    replaced by pseudonyms. Senders &MUST-NOT; combine entries which
     2598   replaced by pseudonyms. Senders &MUST-NOT; combine entries that
    25992599   have different received-protocol values.
    26002600</t>
     
    27832783<t>
    27842784   HTTP/1.1 defaults to the use of "<x:dfn>persistent connections</x:dfn>",
    2785    which allow multiple requests and responses to be carried over a single
     2785   allowing multiple requests and responses to be carried over a single
    27862786   connection. The "<x:ref>close</x:ref>" connection-option is used to signal
    27872787   that a connection will not persist after the current request/response.
     
    28472847</t>
    28482848<t>
    2849    Clients which assume persistent connections and pipeline immediately
     2849   Clients that assume persistent connections and pipeline immediately
    28502850   after connection establishment &SHOULD; be prepared to retry their
    28512851   connection if the first pipelined attempt fails. If a client does
Note: See TracChangeset for help on using the changeset viewer.