{"id":1561,"date":"2022-08-22T11:13:03","date_gmt":"2022-08-22T11:13:03","guid":{"rendered":"https:\/\/www.swifttech.com.np\/blog\/?p=1561"},"modified":"2022-08-22T11:17:59","modified_gmt":"2022-08-22T11:17:59","slug":"http-3-newest-web-protocol","status":"publish","type":"post","link":"https:\/\/www.swifttech.com.np\/blog\/http-3-newest-web-protocol\/","title":{"rendered":"HTTP\/3: Newest web protocol"},"content":{"rendered":"\n

HTTP\/3:<\/strong> In addition to the commonly used HTTP\/1.1 and HTTP\/2, HTTP\/3 is the third main version of the Hypertext Transfer Protocol used to communicate information on the World Wide Web.<\/p>\n\n\n\n

\"\"<\/figure><\/div>\n\n\n\n

HTTP\/3 runs over QUIC \u2013 an encrypted general-purpose transport protocol that multiplexes multiple streams of data on a single connection.<\/p>\n\n\n\n

Google developed QUIC initially . The protocol utilizes space congestion control over User Datagram Protocol (UDP).<\/p>\n\n\n\n

What connection do HTTP, HTTP\/2, and HTTP\/3 have to one another?<\/h2>\n\n\n\n

While HTTP is really \u2018HTTP-over-TCP\u2019 and HTTP\/2 might be described as \u2018HTTP-over-TCP\u2019 then HTTP\/3 might be best described as \u2018HTTP\/2-over-QUIC\u2019.<\/p>\n\n\n\n

During the Black Hat Asia 2020 virtual conference, Google engineer Nick Harper explained in some depth how QUIC and HTTP\/3 compare to HTTP\/2.<\/p>\n\n\n\n

\"\"<\/a>
Need for global security perspectives underlined at virtual event<\/figcaption><\/figure><\/div>\n\n\n\n

Why is it new?<\/h2>\n\n\n\n

HTTP\/3 will be the hypertext transfer protocol’s first significant update.<\/p>\n\n\n\n

The fact that HTTP\/3 utilizes the new transport protocol QUIC is a significant distinction. QUIC is intended for Internet users that are heavily reliant on mobile devices, such as smartphones, which users often switch between as they go about their daily lives. <\/p>\n\n\n\n

When the first Internet protocols were created, devices were less mobile and did not swap networks frequently.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Because of QUIC, HTTP\/3 is dependent on UDP rather than TCP and uses the User Datagram Protocol (UDP) (TCP). By switching to UDP, users will be able to browse the internet more quickly and establish speedier connections.<\/p>\n\n\n\n

Google created the QUIC protocol in 2012, and the vendor-neutral Internet Engineering Task Force (IETF) approved it when they started developing the new HTTP\/3 standard. The IETF has made a number of adjustments to create its own version of QUIC after talking with specialists from all across the world.<\/p>\n\n\n\n

Why is a new version required?<\/h2>\n\n\n\n

QUIC will assist in addressing some of HTTP\/2’s most significant flaws:<\/p>\n\n\n\n

\"\"<\/figure><\/div>\n\n\n\n