𝗗𝗶𝗳𝗳𝗲𝗿𝗲𝗻𝗰𝗲𝘀 𝗯𝗲𝘁𝘄𝗲𝗲𝗻 𝗛𝗧𝗧𝗣/𝟭 𝘃𝘀. 𝗛𝗧𝗧𝗣/𝟮 𝘃𝘀. 𝗛𝗧𝗧𝗣/𝟯 HTTP (The Hypertext Transfer Protocol) is an application protocol used for communicating over the World Wide Web since its introduction in 1989. The first stable version of 𝗛𝗧𝗧𝗣/𝟭.𝟭 was released in 1997 by IETF. Since then, it has become the de facto online communication norm. HTTP utilizes a few simple methods to send and receive information between computers. The two most common ways are GET and POST. Yet, the Internet has changed a lot since 1997. and it demands more from 𝗛𝗧𝗧𝗣/𝟭.𝟭. We now have rich websites, but also HD videos, etc. And we want all pages to load quickly, have better security, etc. HTTP/1 protocol had many issues, such as HOL problems, long HTTP headers, opening many TCP connections for more resources, etc. All this asked for a revision of this protocol, and IETF was published in 2015. a new version, called 𝗛𝗧𝗧𝗣/𝟮, which is the current version. 𝗛𝗧𝗧𝗣/𝟮 introduces header field compression and permits many concurrent exchanges on the same connection, allowing for more effective use of network resources and a decreased feeling of latency. It employs effective coding for HTTP header data and permits the interleaving of request and response messages over the same connection. Additionally, it enables prioritization of requests, enabling more crucial requests to finish faster and enhancing performance. As a result, fewer TCP connections can be used than there were with HTTP/1.x, making the resulting protocol more network-friendly. Longer-lasting connections and reduced competition with other flows result from this, which improves the use of the network's capacity. Finally, 𝗛𝗧𝗧𝗣/𝟮 also 𝘀𝘂𝗽𝗽𝗼𝗿𝘁𝘀 𝗯𝗶𝗻𝗮𝗿𝘆 𝗺𝗲𝘀𝘀𝗮𝗴𝗲 framing allows for more effective message processing. Yet there were some issues with 𝗛𝗧𝗧𝗣/𝟮, such as TCP head-of-line blocking. Other notable problems with 𝗛𝗧𝗧𝗣/𝟮 include the Stream Reuse Attack and the Security Risk of 𝗛𝗧𝗧𝗣/𝟮 Flow Control. The updated HTTP protocol, known as 𝗛𝗧𝗧𝗣/𝟯, was introduced in August 2020. and is based on the QUIC network protocol. This new version of HTTP was introduced to enhance 𝗛𝗧𝗧𝗣/𝟮 by sending encrypted data over UDP, and it seeks to make many significant advancements. 𝗛𝗧𝗧𝗣/𝟯 isn't meant to completely replace 𝗛𝗧𝗧𝗣/𝟮. Instead, it's intended to improve speeds when utilized in specific circumstances. 𝗛𝗧𝗧𝗣/𝟮 can always be used as a backup if 𝗛𝗧𝗧𝗣/𝟯 isn't available. In future posts, we will investigate how HTTP protocols work precisely. _______ If you like my posts, please follow me @milan_milanovic and hit the 🔔 on my profile to get a notification for all my new posts. Grow with me 🚀! #softwareengineering #programming #developers #web #techworldwithmilan