Professional Documents
Culture Documents
STRUCTURE
3.1 INTRODUCTION
3.2 OBJECTIVES
3.3 HTTP
3.4 HTML
3.5 FTP
3.7 TFTP
3.8 SUMMARY
3.1 INTRODUCTION
HTTP is a request/ response protocol. A web client establishes a connection with a Web
server and sends a resource request. The request contains a request method, protocol
version, followed by a MIME-like message. The message contains request modifiers,
client information, and possible body content.
3.2 OBJECTIVES
After reading this unit, you should be able to understand:
a) HTTP
b) FTP
Virtual
HTTP HTTP
Connection
TCP/IP TCP/IP
Protocol Internet Protocol
Suite Suite
Fig. 2 The Web client communicates with the Web server using an
HTTP virtual circuit
Details of HTTP can be found in the following Request for comments (RFC) :
HTTP 1.0 specifications are described in RFC 1945:
http:// www.cis.ohio-state.edu/htbin/rfc/rfc1945.html
MIME specifications are described in RFC 1521:
http:// www.cis.ohio-state.edu/htbin/rfc/rfc1521.html
Graphical
User Web
Interface Resources
Web
HTML Server
HTTP HTTP
TCP/ IP TCP/ IP
Protocol Protocol
Suit Internet Suit
Figure 3 HTML is transported between the web client and web server over the HTTP
virtual connection.
A web client makes a resource request to the Web server, processes the returned
resource, and presents the result through a graphical user interface.
The difference between a server, in client/ server technology, and a Web server seems to
be one accepts requests for data, and the other accepts requests for a resource. The
differences are dramatic as we look closer.
Web
Client
Graphical
User
Interface
Server
Applicati
Database
on Logic
Database
Client Server
Vendor Vendor
Network Network
Software Software
Internet
Web servers receive requests for a resource from Web client through the standard TCP/
IP protocol Suite. The resource can be a file, or data returned by another process. The
Web server locates the file and returns it, or executes another process, supplies it with
input, and returns the output. The Web client does not apply application logic to the
resource. It presents the resource through a graphical user interface. This is a “thin client”
because it does not contain application logic. Figure 5 illustrates Web client/ server
components.
Client
Client
Graphical Web
User Resources
Interface
Database
Web
Server
Client
TCP/ IP TCP/ IP
Protocol Protocol
Internet
Suit Suit
User
This provides a user interface and drives the client protocol interpreter.
Interface
This is the client protocol interpreter. It issues commands to the remote server
Client PI
protocol interpreter and it also drives the client data transfer process.
This is the client data transfer process responsible for communicating with
Client DTP
the server data transfer process and the local file system.
This is the server data transfer process responsible for communicating with
Server DTP
the client data transfer process and the remote file system.
User
User
I/F
Server
FTP Commands User PI
PI
FTP Replies
File File
System System
Server
Data
User
DTP
DTP
Connection
RFC 959 refers to the user rather than the client. RFC 959 defines the means by which
the two PIs talk to each other and by which the two DTPs talk to each other. The user
interface and the mechanism by which the PIs talk to the DTPs are not part of the
standard. It is common practice for the PI and DTP functionalities to be part of the same
program but this is not essential.
During an FTP session there will be two separate network connections one between the
PIs and one between the DTPs. The connection between the PIs is known as the control
connection. The connection between the DTPs is known as the data connection.
Control
a Control dataata
Client Data
Server
TCP
/IP
Inte
rnet
The use of separate connections for control and data offers the advantages that the two
connections can select different appropriate qualities of service e.g. minimum delay for
the control connection and maximum throughput for the data connection, it also avoids
problems of providing escape and transparency for commands embedded within the data
stream.
When a transfer is being set up it always initiated by the client, however either the client
or the server may be the sender of data. As well as transferring user requested files, the
data transfer mechanism is also used for transferring directory listings from server to
client.
3.8 SUMMARY
In normal Internet operation the FTP server listens on the well-known port number 21 for
control connection requests. The choice of port numbers for the data connection depends
on the commands issued on the control connection. Conventionally the client sends a
control message which indicates the port number on which the client is prepared to
accept an incoming data connection request.