Changeset 899
- Timestamp:
- 24/07/10 06:33:10 (12 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.xml
r881 r899 544 544 </section> 545 545 546 <section title="HTTP architecture" anchor="architecture">546 <section title="HTTP-related architecture" anchor="architecture"> 547 547 <t> 548 548 HTTP was created for the World Wide Web architecture … … 552 552 </t> 553 553 554 <section title="Client/Server Operation" anchor="operation">554 <section title="Client/Server Messaging" anchor="operation"> 555 555 <iref item="client"/> 556 556 <iref item="server"/> 557 557 <iref item="connection"/> 558 558 <t> 559 HTTP is a request/response protocol that operates by exchanging messages560 across a reliable transport or session-layer connection. An HTTP client561 is a program that establishes a connection to a server for the purpose562 of sending one or more HTTP requests. An HTTP server is a program that563 accepts connections in order to service HTTP requests by sending HTTP564 responses.559 HTTP is a stateless request/response protocol that operates by exchanging 560 messages across a reliable transport or session-layer connection. An HTTP 561 "client" is a program that establishes a connection to a server for the 562 purpose of sending one or more HTTP requests. An HTTP "server" is a 563 program that accepts connections in order to service HTTP requests by 564 sending HTTP responses. 565 565 </t> 566 566 <iref item="user agent"/> 567 567 <iref item="origin server"/> 568 568 <t> 569 Note that the terms "client" and "server"refer only to the roles that569 Note that the terms client and server refer only to the roles that 570 570 these programs perform for a particular connection. The same program 571 571 may act as a client on some connections and a server on others. We use … … 578 578 Most HTTP communication consists of a retrieval request (GET) for 579 579 a representation of some resource identified by a URI. In the 580 simplest case, this may be accomplished via a single connection (v)581 between the user agent (UA) and the origin server (O).580 simplest case, this may be accomplished via a single bidirectional 581 connection (===) between the user agent (UA) and the origin server (O). 582 582 </t> 583 583 <figure><artwork type="drawing"> 584 request chain ------------------------>585 UA -------------------v-------------------O586 <----------------------- response chain584 request > 585 UA ======================================= O 586 < response 587 587 </artwork></figure> 588 588 <iref item="message"/> … … 644 644 </t> 645 645 <figure><artwork type="drawing"> 646 request chain -------------------------------------->647 UA -----v----- A -----v----- B -----v----- C -----v-----O648 <------------------------------------- response chain646 > > > > 647 UA =========== A =========== B =========== C =========== O 648 < < < < 649 649 </artwork></figure> 650 650 <t> … … 672 672 </t> 673 673 <t><iref item="proxy"/> 674 A proxyis a message forwarding agent that is selected by the674 A "proxy" is a message forwarding agent that is selected by the 675 675 client, usually via local configuration rules, to receive requests 676 676 for some type(s) of absolute URI and attempt to satisfy those … … 683 683 </t> 684 684 <t><iref item="gateway"/><iref item="reverse proxy"/> 685 A gateway (a.k.a., reverse proxy) is a receiving agent that acts685 A "gateway" (a.k.a., "reverse proxy") is a receiving agent that acts 686 686 as a layer above some other server(s) and translates the received 687 687 requests to the underlying server's protocol. Gateways are often … … 699 699 </t> 700 700 <t><iref item="tunnel"/> 701 A tunnelacts as a blind relay between two connections701 A "tunnel" acts as a blind relay between two connections 702 702 without changing the messages. Once active, a tunnel is not 703 703 considered a party to the HTTP communication, though the tunnel may … … 715 715 Any party to HTTP communication that is not acting as a tunnel may 716 716 employ an internal cache for handling requests. 717 A cacheis a local store of previous response messages and the717 A "cache" is a local store of previous response messages and the 718 718 subsystem that controls its message storage, retrieval, and deletion. 719 719 A cache stores cacheable responses in order to reduce the response … … 730 730 </t> 731 731 <figure><artwork type="drawing"> 732 request chain ---------->733 UA -----v----- A -----v-----B - - - - - - C - - - - - - O734 <--------- response chain732 > > 733 UA =========== A =========== B - - - - - - C - - - - - - O 734 < < 735 735 </artwork></figure> 736 736 <t><iref item="cacheable"/> 737 A response is cacheableif a cache is allowed to store a copy of737 A response is "cacheable" if a cache is allowed to store a copy of 738 738 the response message for use in answering subsequent requests. 739 739 Even when a response is cacheable, there may be additional
Note: See TracChangeset
for help on using the changeset viewer.