The head of the Engineering Task Force HTTP Working Group, Mark Nottingham, announced in his personal blog about the completion of the HTTP / 2 protocol, which will change the browsing experience of all of us
The work on the HTTP / 2 protocol done by the IETF (or Engineering Task Force HTTP Working Group) is over - get ready for faster and more secure internet than ever before. The new HTTP / 2 protocol, which will replace the current HTTP / 1.1 protocol, comes with a number of improvements and upgrades such as: New options called "Multiplexing" and "Header Compression" allow a particular browser to send several requests to the server simultaneously.
The HTTP / 2 protocol also enables a simpler connection between the user and the server, which can now be performed with fewer active connections and connections since Active are able to connect the servers directly to the browser, enabling faster and more cost-effective browsing. This direct and cost-effective transfer can, for example, send CSS information of a particular site to the user's browser before it is requested, saving time for both the user and the server itself.
According to Nottingham, head of the IETF group, the HTTP / 2 protocol does not require SSL / TLS encryption for all sites that use it. Nonetheless, adjustments and optimizations for better TLS encryption support will come with the new protocol, support that matches the statements of Google And Mozilla (creators of the browserChrome And Firefox), which announced that they would only support HTTP / 2 browsing under TLS security.
Although the vast majority of work on the HTTP / 2 protocol has been completed, there is a long way to go before this protocol can become an official Internet standard that is expected to replace the SPDY protocol Google In future versions of browser The company's chrome.