http example WWW: the http protocol Internet apps: their protocols and transport protocols Transport service requirements of common apps

Transcription

1 Transport service requirements of common apps Internet apps: their protocols and transport protocols Data loss Bandwidth Time Sensitive layer protocol Underlying transport protocol file transfer e- Web documents real-time audio/video stored audio/video interactive games financial apps no loss no loss no loss audio: 5Kb-1Mb video:10kb-5mb same as above few Kbps up no no no yes, 100 s msec yes, few secs yes, 100 s msec yes and no e- remote terminal access Web file transfer streaming multimedia remote file Internet telephony smtp [RFC 821] telnet [RFC 854] http [RFC 2068] ftp [RFC 959] proprietary (e.g. RealNetworks) NSF proprietary (e.g., Vocaltec) or UDP or UDP typically UDP 2: Layer 6 2: Layer 8 WWW: the http protocol http: hypertext transfer protocol WWW s application layer protocol / model : browser that requests, receives, displays WWW objects : WWW sends objects in response to requests http1.0: RFC 1945 http1.1: RFC 2068 PC running Explorer Mac running Navigator Server running NCSA Web 2: Layer 9 time http example Suppose enters URL 1a. http initiates connection to http (process) at Port 80 is default for http. 2. http sends message (containing URL) into connection socket (contains text, references to 10 jpeg images) 1b. http at host waiting for connection at port 80. accepts connection, notifying 3. http receives request message, forms response message containing requested object (somedepartment/home.index), sends message into socket 2: Layer 11

2 time http example (cont.) 5. http receives response message containing html file, displays html. Parsing html file, findis10 referenced jpeg objects 6. Steps 1-5 repeated for each of 10 jpeg objects 4. http closes connection. non-persistent connection: one object in each connection some browsers create multiple connections simultaneously - one per object persistent connection: multiple objects transferred within one connection 2: Layer 12 http message format: request two types of http messages: request, response message: ASCII (human-readable format) request line (GET, POST, HEAD commands) Carriage return, line feed indicates end of message header lines GET /somedir/page.html HTTP/1.1 Connection: close User-: Mozilla/4.0 Accept: text/html, image/gif,image/jpeg Accept-language:fr (extra carriage return, line feed) 2: Layer 13 message: general format http message format: reply status line (protocol status code status phrase) header lines HTTP/ OK Connection: close Date: Thu, 06 Aug :00:15 GMT Server: Apache/1.3.0 (Unix) Last-Modified: Mon, 22 Jun Content-Length: 6821 Content-Type: text/html data data data data data... data, e.g., requested html file 2: Layer 14 2: Layer 15

3 Trying out http ( side) for yourself 1. Telnet to your favorite WWW : telnet Type in a GET : GET /~ross/index.html HTTP/1.0 Opens connection to port 80 (default http port) at Anything typed in sent to port 80 at By typing this in (hit carriage return twice), you send this minimal (but complete) GET request to http 3. Look at response message sent by http! User- interaction: authentication Authentication goal: control access to documents stateless: must present authorization in each request authorization: typically name, password authorization: header line in request if no authorization presented, refuses access, sends WWW authenticate: header line in response 401: authorization req. WWW authenticate: + Authorization:line usual msg + Authorization:line usual msg time 2: Layer 17 2: Layer 18 User- interaction: cookies Web Caches (proxy ) sends cookie to in response Set-cookie: # present cookie in later requests cookie: # matches presented-cookie with -stored cookies authentication remembering preferences, previous choices usual + Set-cookie: # cookie: # usual msg cookie: # usual msg cookiespectific action cookiespectific action Goal: satisfy request without involving origin sets browser: WWW accesses via web cache sends all http requests to web cache if object at web cache, web cache immediately returns object in http response else requests object from origin, then returns http response to Proxy origin origin 2: Layer 19 2: Layer 21

4 ftp: the file transfer protocol ftp: separate control, data connections at host interface local file system file transfer transfer file to/from remote host / model remote file system : side that initiates transfer (either to/from remote) : remote host ftp: RFC 959 ftp : port 21 ftp contacts ftp at port 21, specifying as transport protocol two parallel connections opened: control: exchange commands, responses between,. out of band control data: file data to/from ftp maintains state : current directory, earlier authentication control connection port 21 data connection port 20 2: Layer 23 2: Layer 24 ftp commands, responses Sample commands: sent as ASCII text over control channel USER name PASS password LIST return list of file in current directory RETR filename retrieves (gets) file STOR filename stores (puts) file onto remote host Sample return codes status code and phrase (as in http) 331 Username OK, password required 125 data connection already open; transfer starting 425 Can t open data connection 452 Error writing file 2: Layer 25 Electronic Mail Three major components: s s simple transfer protocol: smtp User Agent a.k.a. reader composing, editing, reading messages e.g., Eudora, pine, elm, Netscape Messenger outgoing, incoming messages stored on outgoing message queue box 2: Layer 26

5 Electronic Mail: s Electronic Mail: smtp [RFC 821] Mail Servers box contains incoming messages (yet ot be read) for message queue of outgoing (to be sent) messages smtp protocol between to send e messages : sending : receiving uses tcp to reliably transfer e msg from to, port 25 direct transfer: sending to receiving three phases of transfer handshaking (greeting) transfer closure command/response interaction commands: ASCI text response: status code and phrase 2: Layer 27 2: Layer 28 Sample smtp interaction smtp: final words S: 220 hamburger.edu C: HELO crepes.fr S: 250 Hello crepes.fr, pleased to meet you C: MAIL FROM: <alice@crepes.fr> S: 250 alice@crepes.fr... Sender ok C: RCPT TO: <bob@hamburger.edu> S: 250 bob@hamburger.edu... Recipient ok C: DATA S: 354 Enter, end with "." on a line by itself C: Do you like ketchup? C: How about pickles? C:. S: 250 Message accepted for delivery C: QUIT S: 221 hamburger.edu closing connection try smtp interaction for yourself: telnet name 25 see 220 reply from enter HELO, MAIL FROM, RCPT TO, DATA, QUIT commands above lets you send e without using e (reader) Comparison with http http: pull e: push both have ASCII command/response interaction, status codes http: multiple objects in file sent in separate connections smtp: multiple message parts sent in one connection 2: Layer 29 2: Layer 30

6 Mail message format Message format: multimedia extensions smtp: protocol for exchanging e msgs RFC 822: standard for text message format: header lines, e.g., To: From: Subject: different from smtp commands! body the message, ASCII characters only. header body blank line MIME: multimedia extension, RFC 2045, 2056 additional lines in msg header declare MIME content type MIME version method used to encode data multimedia data type, subtype, parameter declaration encoded data From: alice@crepes.fr To: bob@hamburger.edu Subject: Picture of yummy crepe. MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Type: image/jpeg base64 encoded data base64 encoded data. line containing only `. 2: Layer 31 2: Layer 32 MIME types Mail access protocols Text example subtypes: plain, html Image example subtypes: jpeg, gif Audio exampe subtypes: basic (8-bit mu-law encoded), 32kadpcm (32 kbps coding) Video example subtypes: mpeg, quicktime other data that must be processed by reader before viewable example subtypes: msword, octet-stream POP3 or IMAP sender s receiver s : delivery/storage to receiver s Mail access protocol: retrieval from POP: Post Office Protocol [RFC 1939] authorization ( <-->) and download IMAP: Internet Mail Access Protocol [RFC 1730] more features (more complex) manipulation of stored msgs on 2: Layer 33 2: Layer 34

7 POP3 protocol authorization phase commands: : declare name pass: password responses +OK -ERR transaction phase, : list: list message numbers retr: retrieve message by number dele: delete quit S: +OK POP3 ready C: alice S: +OK C: pass hungry S: +OK successfully logged on C: list S: S: S:. C: retr 1 S: <message 1 contents> S:. C: dele 1 C: retr 2 S: <message 1 contents> S:. C: dele 2 C: quit S: +OK POP3 signing off 2: Layer 35