Why the new HTTP is different and why the world should care
Switching to HTTP/2
It will probably take several years for the whole Internet to switch over to HTTP/2. The new protocol only works if both the client and server support it.
For this reason, you can expect the old and new HTTP to coexist in parallel for the foreseeable future. Practically speaking, this dual functionality means web browsers will initially contact a server with the old version 1.1 and then use HTTP/2 if the server supports it.
Browsers currently use an encrypted HTTP message to initiate a request to upgrade to HTTP/2. If a server accepts the request, the connection automatically switches to HTTP/2. However, the use of TLS is not necessarily required for HTTP/2. According to the specification, the connection can also use an unencrypted HTTP/2 connection via TCP.
In an effort to strengthen encryption on the web, major browser manufacturers Mozilla and Google currently only support HTTP/2 in combination with TLS. The specification requires TLS 1.2 or later for TLS connections, and data compression with TLS is not allowed.
You can visit the Akamai website [7] to find out if your web browser already supports HTTP/2. If you visit the site with a suitable web browser, you will see an impressive demo that shows how quickly images load using HTTP/2 instead of HTTP/1.1.
Outlook
HTTP/2 offers advantages for both users and web servers because both sides can save significant storage space and CPU time. Technologies for reducing the number of resources, for example, CSS Sprites and resource inlining, will no longer be necessary. The full impact of the new HTTP standard won't be known until its new functions are fully integrated into web APIs.
Infos
- RFC 2616: https://www.ietf.org/rfc/rfc2616.txt
- Average Number of Web Page Objects: http://www.websiteoptimization.com/speed/tweak/average-number-web-objects/
- Hypertext Transfer Protocol, Version 2: https://httpwg.github.io/specs/rfc7540.html
- SPDY Protocol: http://tools.ietf.org/html/draft-mbelshe-httpbis-spdy-00
- Header Compression for HTTP/2: https://httpwg.github.io/specs/rfc7541.html
- HTTP/2 FAQ: https://http2.github.io/faq/#is-it-http20-or-http2
- Test Page: https://http2.akamai.com/demo
« Previous 1 2
Buy this article as PDF
(incl. VAT)