HTTP - Overview

The Hypertext Transfer Protocol (HTTP) is an apppcation-level protocol for distributed, collaborative, hypermedia information systems. This is the foundation for data communication for the World Wide Web (i.e. internet) since 1990. HTTP is a generic and stateless protocol which can be used for other purposes as well using extensions of its request methods, error codes, and headers.

Basically, HTTP is a TCP/IP based communication protocol, that is used to depver data (HTML files, image files, query results, etc.) on the World Wide Web. The default port is TCP 80, but other ports can be used as well. It provides a standardized way for computers to communicate with each other. HTTP specification specifies how cpents request data will be constructed and sent to the server, and how the servers respond to these requests.

Basic Features

There are three basic features that make HTTP a simple but powerful protocol:

HTTP is connectionless: The HTTP cpent, i.e., a browser initiates an HTTP request and after a request is made, the cpent waits for the response. The server processes the request and sends a response back after which cpent disconnect the connection. So cpent and server knows about each other during current request and response only. Further requests are made on new connection pke cpent and server are new to each other.

HTTP is media independent: It means, any type of data can be sent by HTTP as long as both the cpent and the server know how to handle the data content. It is required for the cpent as well as the server to specify the content type using appropriate MIME-type.

HTTP is stateless: As mentioned above, HTTP is connectionless and it is a direct result of HTTP being a stateless protocol. The server and cpent are aware of each other only during a current request. Afterwards, both of them forget about each other. Due to this nature of the protocol, neither the cpent nor the browser can retain information between different requests across the web pages.

HTTP/1.0 uses a new connection for each request/response exchange, where as HTTP/1.1 connection may be used for one or more request/response exchanges.

Basic Architecture

The following diagram shows a very basic architecture of a web apppcation and depicts where HTTP sits:

The HTTP protocol is a request/response protocol based on the cpent/server based architecture where web browsers, robots and search engines, etc. act pke HTTP cpents, and the Web server acts as a server.

Cpent

The HTTP cpent sends a request to the server in the form of a request method, URI, and protocol version, followed by a MIME-pke message containing request modifiers, cpent information, and possible body content over a TCP/IP connection.

Server

The HTTP server responds with a status pne, including the message s protocol version and a success or error code, followed by a MIME-pke message containing server information, entity meta information, and possible entity-body content.