Computer Networks. HTTP and more. Jianping Pan Spring /20/17 CSC361 1

Size: px

Start display at page:

Download "Computer Networks. HTTP and more. Jianping Pan Spring /20/17 CSC361 1"

Nicholas Leonard
6 years ago
Views:

1 Computer Networks HTTP and more Jianping Pan Spring /20/17 CSC361 1

2 First things first W1 due next Monday (Jan 23) submit a single PDF file through connex Noah posted a docx for for questions on xc feel free to discuss online and offline but do write you own answers how's the lab this week? how's your P1 progress? 1/20/17 CSC361 2

3 Last lecture Web, URL, HTML and HTTP basics the application-layer protocol for the Web follow the client-server model (stateless) request-reply transaction HTTP request: GET / HTTP/1.0 HTTP response: HTTP/ OK the service expected from lower layers reliable data transfer normally by TCP 1/20/17 CSC361 3

4 Web browsing examples <html> <img src='' <a ref='' <img src='' </html> In your favorite web browser URL: Q: how many HTTP requests? 1/20/17 CSC361 4 discussion on blackboard

5 Today's topics HTTP: advanced topics fit better on TCP improve HTTP efficiency become stateful server and client can know/remember each other deal with scalability web caching and content delivery 1/20/17 CSC361 5

6 HTTP/TCP TCP connection establishment client: connect(); server: accept() HTTP transaction request: client: send(); server: recv() response: server: send(); client: recv() TCP connection release Q: round-trips? server: close(); client: close() Client is to retrieve the embedded objects 1/20/17 CSC361 6

7 Example <html> <img src='' <a ref='' <img src='' </html> 1/20/17 CSC361 7

8 Non-persistent HTTP One object per TCP connection default behavior in HTTP/1.0 network cost: ~2*RTT per object end-host cost: 1 socket() for each object Performance improvement parallel/concurrent connections e.g., an HTML page with 2 embedded objects Q: cost reduced? 1/20/17 CSC361 8 Figure on blackboard

9 Persistent HTTP Multiple objects through a TCP connection between the same client/server default behavior in HTTP/1.1 for HTTP/1.0: Connection: Keep-Alive network cost: ~RTT per object for many objects to disable/close: Connection: Close client/server Keep-Alive timeout Performance improvement: pipelining Q: pros and cons? ~2*RTT for all objects from the same server 1/20/17 CSC361 9 Figure on blackboard

10 Client-server states HTTP itself is stateless request-reply transactions Many applications require states cookie issued by server s backend servers HTTP response header: Set-Cookie client can choose to keep cookie client presents cookie in subsequent requests HTTP request header: Cookie 1/20/17 CSC361 10

11 HTTP cookies: an example client server ebay 8734 cookie file ebay 8734 amazon 1678 one week later: ebay 8734 amazon 1678 usual http request msg usual http response Set-cookie: 1678 usual http request msg cookie: 1678 usual http response msg usual http request msg cookie: 1678 usual http response msg Amazon server creates ID 1678 for user create entry cookiespecific action cookiespectific action 1/20/17 CSC access access backend database

12 Tracking client?! Between web servers HTTP request header: Referer Referrer! referrer spamming and referrer spoofing de-referring User security and privacy e.g., cookie theft, cookie poisoning, web bug browsing anonymizing 1/20/17 CSC361 12

13 server Web caching client Proxy Scalability issues with the client-server model one server, many clients, concurrent requests server load network traffic Web caching: aggregate user requests by caching responses to previous requests explore locality: same requests may occur soon! reduce response time and traffic load client 1/20/17 CSC Example on blackboard

14 Consistency control Objects retrieved from the cache may be staled due to updates at origin servers Strong consistency HTTP request header: If-Modified-Since HTTP response: HTTP/ Not Modified reduce traffic load if hit Weak consistency Q: pros and cons? time-to-live (TTL) reduce traffic load and response time if hit 1/20/17 CSC361 14

15 Conditional GET Goal: don t send object if cache has up-to-date cached version cache: specify date of cached copy in HTTP request If-modified-since: <date> server: response contains no object if cached copy is up-todate: HTTP/ Not Modified cache HTTP request msg If-modified-since: <date> HTTP response HTTP/ Not Modified HTTP request msg If-modified-since: <date> HTTP response HTTP/ OK <data> 1/20/17 CSC server object not modified object modified

16 Content delivery Move content closer to end users content distribution Redirect users to closer servers information retrieval how do they do that? e.g., Akamai DNS-based server selection more after DNS lectures 1/20/17 CSC361 16

17 This lecture HTTP (non-)persistence, pipelining, cookies, referrers web caching and content delivery Explore further How do your favorite web browsers and servers support advanced HTTP features? bonus features in your P1? 1/20/17 CSC361 17

18 Next lecture DNS DNS server hierarchy DNS resolution process DNS-based server selection 1/20/17 CSC361 18

Internet applications

CSc 450/550 Computer Networks Worldwide Web Jianping Pan Summer 2006 5/18/06 CSc 450/550 1 Traditionally Internet applications remote login: e.g., telnet file transfer: e.g., FTP electronic mail: e.g.,