Changeset 2074 for draft-ietf-httpbis/latest/p1-messaging.xml
- Timestamp:
- 31/12/12 11:51:04 (9 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.xml
r2072 r2074 575 575 applicable to that request. The following illustrates the resulting 576 576 chain if B has a cached copy of an earlier response from O (via C) 577 for a request whichhas not been cached by UA or A.577 for a request that has not been cached by UA or A. 578 578 </t> 579 579 <figure><artwork type="drawing"> … … 2596 2596 Senders &SHOULD-NOT; combine multiple entries unless they are all 2597 2597 under the same organizational control and the hosts have already been 2598 replaced by pseudonyms. Senders &MUST-NOT; combine entries which2598 replaced by pseudonyms. Senders &MUST-NOT; combine entries that 2599 2599 have different received-protocol values. 2600 2600 </t> … … 2783 2783 <t> 2784 2784 HTTP/1.1 defaults to the use of "<x:dfn>persistent connections</x:dfn>", 2785 which allowmultiple requests and responses to be carried over a single2785 allowing multiple requests and responses to be carried over a single 2786 2786 connection. The "<x:ref>close</x:ref>" connection-option is used to signal 2787 2787 that a connection will not persist after the current request/response. … … 2847 2847 </t> 2848 2848 <t> 2849 Clients whichassume persistent connections and pipeline immediately2849 Clients that assume persistent connections and pipeline immediately 2850 2850 after connection establishment &SHOULD; be prepared to retry their 2851 2851 connection if the first pipelined attempt fails. If a client does
Note: See TracChangeset
for help on using the changeset viewer.