0% found this document useful (0 votes)
112 views4 pages

Chapter 22

The document describes the Hypertext Transfer Protocol (HTTP) and interactions between clients, proxies, and servers on the World Wide Web. It provides examples of common HTTP request and response codes to transfer documents and files. It also illustrates message flows and caching by proxies to improve performance and availability of frequently requested resources.

Uploaded by

Siraj Ud-Doulla
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
112 views4 pages

Chapter 22

The document describes the Hypertext Transfer Protocol (HTTP) and interactions between clients, proxies, and servers on the World Wide Web. It provides examples of common HTTP request and response codes to transfer documents and files. It also illustrates message flows and caching by proxies to improve performance and availability of frequently requested resources.

Uploaded by

Siraj Ud-Doulla
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

CHAPTER 22

World Wide Web and HTTP

1.
a. GET /usr/users/doc/doc.1 HTTP /1.1
Date: Fri, 26-Nov-04 16:46:23 GMT
MIME-version: 1.0
Accept: image/gif
Accept: image/jpeg
Last modified: Mon, 22-Nov-04
b. HTTP/1.1 200 OK
Date: Fri, 26-Nov-04 16:46:26 GMT
Server: Challenger
MIME-version: 1.0
Content-length: 4623
(Body of document)
c. HTTP/1.1 302 Moved permanently
Date: Fri, 26-Nov-04 16:46:26 GMT
Server: Challenger
Location: /usr/deads/doc.1
d. HTTP/1.1 400 Bad Request
Date: Fri, 26-Nov-04 16:46:26 GMT
Server: Challenger
e. HTTP/1.1 401 Unauthorized
Date: Fri, 26-Nov-04 16:46:26 GMT
Server: Challenger
3.
a.
COPY /bin/usr/bin/file1 HTTP /1.1
Date: Fri, 26-Nov-04 17:07:15 GMT
MIME-version: 1.0
Location: /bin/file1

1
2

b.
HTTP/1.1 200 OK
Date: Fri, 26-Nov-04 17:07:22 GMT
Server: Challenger
5.
a. GET /bin/etc/file1 HTTP /1.1
Date: Fri, 26-Nov-04 17:29:42 GMT
MIME-version: 1.0
Accept: */*
If-modified-since: 23-Jan-99 00:00:00 GMT
b. HTTP/1.1 200 OK
Date: Fri, 26-Nov-04 17:29:49 GMT
Server: Challenger
MIME-version: 1.0
Content-length: 2686
(Body of document)
7. Normally eight segments are exchanged for this transaction as shown in Figure
22.E7.
Figure 22.E7 Solution to Exercise 7

HTTP TCP Client TCP Server HTTP


client Server

Passive
open
Active 1 SYN
open
SYN + ACK 2

3 ACK

Request 4 Request
Dynamic
document Static Document + ACK 5

Active
close 6 FIN
Passive
FIN + ACK 7 close
8 ACK

Time Time Time Time

9. Figure 22.E9 shows a simple situation. A portal, such as Yahoo, is a special site
that holds the often-visited URLs for each client. The cookie stored in the browser
under the name of the portal, holds the list of the sites the user normally needs to
check periodically. When the user clicks on the portal web page, a request is sent
with the cookie to the portal site with the list of desired web pages. The portal then
fetches the current pages from the corresponding site, compiles a page, and sends
it to the browser.
3

Figure 22.E9 Solution to Exercise 9

Portal Client
cookie Portal Site 1 Site 2
Site 1
Site 2

Request
1 + cookie
2 Request

3
P1
4 Request

5
6 P2
P1 P2

11. Figure 22.E11 shows a simple example. We assume the computer has installed
Figure 22.E11 Solution to Exercise 11

Client Proxy

Server
Request
1
Response
2

Internet

Client Proxy Solution to part a


Server

Request
1
Request
2
Response
3

Response Add resposne


4 to the cache

Internet

Solution to part b

both the client HTTP and the proxy server HTTP. In part a, the request can be
4

responded by the proxy server. In part b, the proxy needs to send the request to the
true server. When the response is received, the proxy server saves it in the cache
for future use, and then sends it to the client.
13. Figure 22.E13 shows a simple example. We assume that the client is connected via
a point-to-point WAN to an ISP network. The proxy server is installed in the proxy
server. In part a, the request can be responded by the proxy server. In part b, the
proxy needs to send the request to the true server. When the response is received,
the proxy server saves it in the cache, for future use, and then sends it to the client.

Figure 22.E13 Solution to Exercise 13

Client Proxy Server

Request
1
Response
2

ISP

Point-to-point
WAN
Internet

Solution to part a

Client Proxy Server

Request
1
Request
2
Response
3

Add resposne
Response to the cache
4

ISP

Point-to-point
WAN
Internet

Solution to part b

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy