WWW and HTTP
ARCHITECTURE
The WWW today is a distributed client/server service,
in which a client using a browser can access a service
using a server. However, the service provided is
distributed over many locations called sites.
Topics discussed in this section:
Client (Browser)
Server
Uniform Resource Locator
Cookies
27.2
Architecture of WWW
27.3
Browser
27.4
URL
27.5
WEB DOCUMENTS
The documents in the WWW can be grouped into three
broad categories: static, dynamic, and active. The
category is based on the time at which the contents of
the document are determined.
Topics discussed in this section:
Static Documents
Dynamic Documents
Active Documents
27.6
Static document
27.7
Boldface tags
27.8
Effect of boldface tags
27.9
Beginning and ending tags
27.10
Dynamic document using CGI
27.11
Dynamic document using server-site script
27.12
Note
Dynamic documents are sometimes
referred to as server-site dynamic
documents.
27.13
Active document using Java applet
27.14
Active document using client-site script
27.15
Note
Active documents are sometimes
referred to as client-site dynamic
documents.
27.16
HTTP
The Hypertext Transfer Protocol (HTTP) is a protocol
used mainly to access data on the World Wide Web.
HTTP functions as a combination of FTP and SMTP.
Topics discussed in this section:
HTTP Transaction
Persistent Versus Nonpersistent Connection
27.17
Note
HTTP uses the services of TCP on
well-known port 80.
27.18
HTTP transaction
27.19
Request and response messages
27.20
Request and status lines
27.21
Methods
27.22
Status codes
27.23
Status codes (continued)
27.24
Header format
27.25
General headers
27.26
Request headers
27.27
Response headers
27.28
Entity headers
27.29
Example 1
This example retrieves a document. We use the GET
method to retrieve an image with the path /usr/bin/image1.
The request line shows the method (GET), the URL, and
the HTTP version (1.1). The header has two lines that
show that the client can accept images in the GIF or
JPEG format. The request does not have a body. The
response message contains the status line and four lines of
header. The header lines define the date, server, MIME
version, and length of the document. The body of the
document follows the header (see Figure 27.16).
27.30
Figure Example 1
27.31
Example.2
In this example, the client wants to send data to the
server. We use the POST method. The request line shows
the method (POST), URL, and HTTP version (1.1). There
are four lines of headers. The request body contains the
input information. The response message contains the
status line and four lines of headers. The created
document, which is a CGI document, is included as the
body (see Figure 27.17).
27.32
Figure Example.2
27.33
Example 3
HTTP uses ASCII characters. A client can directly
connect to a server using TELNET, which logs into port
80 (see next slide). The next three lines show that the
connection is successful. We then type three lines. The
first shows the request line (GET method), the second is
the header (defining the host), the third is a blank,
terminating the request. The server response is seven
lines starting with the status line. The blank line at the
end terminates the server response. The file of 14,230
lines is received after the blank line (not shown here).
The last line is the output by the client.
27.34
Example 3 (continued)
27.35
Note
HTTP version 1.1 specifies a persistent
connection by default.
27.36
