HTTP full form? Hypertext Transfer Protocol

HTTP full form

Hypertext Transfer Protocol

HTTP full form is Hypertext Transfer Protocol. it’s the protocol used to transfer files between a web server and a browser. When you type in a web address, like “www.google.com”, your browser uses HTTP to connect to Google’s servers and request the web page you want to see.

What is hypertext

Hypertext is the text that links to other text. When you click on a hyperlink, your browser will connect to the other text and display it on the screen. Hypertext is used all over the web because it makes it easy for people to navigate between different web pages.

AD full form

How HTTP works

HTTP works by sending requests from a browser to a web server. When you type in a web address, your browser sends a request to the server asking for the web page you want to see. The server then responds by sending the HTML code for the web page back to the browser. The browser then displays the web page on the screen.

This way of requesting data is rather slow, and the requests can only be sent one after another. To speed things up, browsers send multiple requests at once by opening multiple connections with the webserver. This is called HTTP Pipelining.

This means that your browser will open an initial connection with a web server to request a small object like a banner ad, and then open another connection to request a larger object like an image or a news article. 

Web servers use HTTP Keep-Alive to keep the initial TCP connections open so that they can reuse them for subsequent requests. This way, instead of opening multiple TCP connections, the browser only opens one TCP connection for all the objects requested.

The server sends the large objects in a stream, one after another. The browser interprets the stream and presents it as a series of small requests and responses.

HTTP Pros:

-HTTP is a fast and easy way to transfer files between a web server and a browser.

-HTTP keeps the initial TCP connections open so that multiple requests can be sent at once.

-HTTP Pipelining allows browsers to send multiple requests at once.

-Web servers use HTTP Keep-Alive to keep the initial TCP connections open.

HTTP Cons:

-HTTP requests can only be sent one after another.

-A single TCP connection can only send data in one direction at a time and is slower than UDP.

-Server and browser must use multiple connections to speed up long downloads: One for control messages and head/parsing files, and another that sends the data.

HTTP history

The HyperText Transfer Protocol (HTTP) is an application protocol for distributed, collaborative, hypermedia information systems. HTTP is the foundation of data communication for the World Wide Web.

The first version of HTTP was introduced in 1991 by Tim Berners-Lee and his team at CERN. It was called HTTP 0.9. The main improvement in HTTP 1.0, which was released in 1996, was the addition of chunked transfer encoding and persistent connections.

HTTP 1.1, which was introduced in 1997, included more improvements such as support for byte serving, better error handling, and updated header fields. In 1999, RFC 2616 updated the HTTP 1.1 standard.

HTTP 2.0 was published as RFC 7540 on May 14, 2015, and it includes several improvements over the previous version of HTTP.

HTTP 3.0 is based on the previous draft proposal for QUIC — an experimental transport layer network protocol developed by Google Inc.

HTTPS is a fast and easy way to transfer files between a web server and a browser. HTTPS keeps the initial TCP connections open so that multiple requests can be sent at once. HTTP Pipelining allows browsers to send multiple requests at once. Web servers use HTTP Keep-Alive to keep the initial TCP connections open.

Leave a Comment