HTTP is a protocol used to access data on the World Wide Web. Tim Berners-Lee initially developed HTTP in 1989 while working at CERN. HTTP follows a client-server model where a client (usually a web browser) sends an HTTP request to a server, which then returns an HTTP response. The standard port for HTTP is 80. HTTP allows for the transfer of text, audio, video, and other data over the internet.

1. HTTP PROTOCOL
Made By-
Name – Abshar Fatima
Enroll no. – 42907
Class – TYBSc(CS)
Divison –’B’

2. WHAT IS HTTP ?
• HTTP stands for Hyper Text Transfer Protocol.
• It is a protocol used to access the data on the World Wide Web
(WWW).
• The HTTP protocol can be used to transfer the data in the form of
plain text, hypertext, audio, video, and so on.
• HTTP is an "application layer" protocol.
• HTTP follows a classical "client-server" model.
• HTTP is a TCP/IP based communication protocol.
• The standard port for HTTP connections is port 80.
• The version of HTTP in common use is HTTP/1.1
• HTTP/2 was published in May 2015.

3.  Development of HTTP was initiated by Tim Berners-Lee, a
British scientist at CERN in 1989 and summarized in a simple
document describing the behavior of a client and a server using
the first HTTP protocol version that was named 0.9.
 CERN : The European Organization for Nuclear Research
WHO DEVELOPED THE HTTP ?

4. World Wide Web Communication….
The World Wide Web is about communication between
web clients and web servers.
Clients are often browsers (Chrome, Edge, Safari), but they can
be any type of program or device.
Servers are most often computers in the cloud.
Communication between client computers and web servers is
done by sending HTTP Requests and receiving HTTP Responses.

5. HTTP Request / HTTP Response
Communication between clients and servers is done
by requests and responses:
• A client (a browser) sends an HTTP request to the web.
• A web server receives the request.
• The server runs an application to process the request.
• The server returns an HTTP response (output) to the
browser.
• The client (the browser) receives the response.
• HTTP Requests are messages which are sent by the client or user to initiate
an action on the server.
• HTTP Response sent by a server to the client. The response is used to
provide the client with the resource it requested. It is also used to inform
the client that the action requested has been carried out. It can also inform
the client that an error occurred in processing its request.

6. HOW DOES HTTP WORKS ?
Whenever we issue a URL from our browser to get a web resource using HTTP,
e.g. http://www.ellipse.com/index.html, the browser turns the URL into a request message and
sends it to the HTTP server. The HTTP server interprets the request message, and returns you an
appropriate response message, which is either the resource you requested or an error message.
This process is illustrated below:
A URL (Uniform
Resource Locator) is
used to uniquely
identify a resource over
the web.
URL has the following
syntax:
protocol://hostname:p
ort/path-and-file-
name

7. FEATURES OF HTTP
 Connectionless protocol: HTTP is a connectionless protocol. HTTP client
initiates a request and waits for a response from the server. When the server
receives the request, the server processes the request and sends back the
response to the HTTP client after which the client disconnects the connection.
The connection between client and server exist only during the current request
and response time only.
 Media independent: HTTP protocol is a media independent as data can be sent
as long as both the client and server know how to handle the data content. It is
required for both the client and server to specify the content type in MIME-type
header.
 Stateless: HTTP is a stateless protocol as both the client and server know each
other only during the current request. Due to this nature of the protocol, both
the client and server do not retain the information between various requests of
the web pages.

8. Advantages of HTTP
 Addressing
HTTP uses advanced scheme of addressing. It assigns IP address with recognizable names so that it can be
identified easily in the World Wide Web. Compared to the standard procedure of IP address with a series of
numbers, using this the public can easily engage with the internet.
 Flexibility
Whenever there are additional capabilities needed by an application, HTTP has the capability to download
extensions or plugins and display the relevant data. These can include Flash players and Acrobat reader.
 Security
In HTTP each files is downloaded from an independent connection and then gets closed. Due to this no more
than one single element of a webpage gets transferred. Therefore, the chance of interception during
transmission is minimized here.
 Latency
Only when the connection is established, the handshaking process will take place in HTTP. Hence, there will be
no handshaking procedure following a request. This significantly reduces latency in the connection.
 Accessibility
When the page is loaded for the first time, all of the HTTP pages gets stored inside the internet caches known
as the page cache. Therefore, once the page is visited again, the content is loaded quickly.

9. Disadvantages of HTTP
 Data Integrity
Since there are no any encryption methods used in HTTP, there are chances of someone altering the
content. That is the reason why HTTP is considered to be an insecure method prone to data integrity.
 Data Privacy
Privacy is another problem faced in a HTTP connection. If any hacker manages to intercept the request
they can view all the content present in the web page. Besides that they can also gather confidential
information such as the username and the password.
 Server Availability
Even if HTTP receives all the data that it needs, clients does not take measures to close the connection.
Therefore, during this time period, server will not be present.
 Administrative Overhead
For transmitting a web page, a HTTP needs to create multiple connections. This causes administrative
overhead in the connection.
 IoT Device Support
HTTP uses more number of system resources which leads to more power consumption. Since IoT device
today contain wireless sensor networks, it is not suitable to use HTTP.