What Is HTTP2?

what is http2
HTTP/2 is simply an update to the protocol, but is really a huge deal because the last time the HTTP specification was updated back in 1999. This means the HTTP/2 will be the first major update to the HTTP standard over the last 16 years, marking the largest change since 1999 when HTTP 1.1 was adopted that underpins the World Wide Web as we know it today.

HTTP/2 promises to deliver Web pages to browsers faster, allowing online users to read more pages, buy more things and perform more and faster Internet searches.

HTTP/2 is based on SPDY protocol, a protocol introduced by Google in 2009 and adopted by some technologies including Google’s own Chrome browser, Mozilla’s Firefox, Microsoft’s Internet Explorer, many websites such as Facebook, and some of the software that delivers Web pages to browsers.

SPDY (fittingly pronounced “speedy”) was designed to speed up the loading of web pages and the browsing experience of the online users. Both SPDY and HTTP/2 use “header field compression” and “multiplexing” to let browsers make multiple requests to web servers via a single connection.

HTTP/2 won’t replace the traditional web standard what the world knows and loves, but it is expected to help websites load faster and more securely once it’s adopted a wide scale.
HTTP 2.0 also brings another big change – Encryption. It was originally planned to push encryption technology called TLS (Transport Layer Security, formerly called SSL for Secure Sockets) in HTTP/2, but this was rejected because of inconvenience to certain network operators and proxy vendors by burdening them with new standards.

How Does HTTP2 Improve On HTTP?

The first thing users might notice with HTTP2 are faster load times on existing websites, thanks to a multiplexing feature that can deliver more HTTP requests at once.

Currently, many developers minimize HTTP requests with hacks like spriting and inlining, which cut down on those requests by, for instance, combining several images into a single file that gets loaded all at once. But these hacks can create their own problems—and anyway, no one should have to hack a good protocol just to give users barely acceptable performance. With HTTP 2, a larger number of requests is no longer a problem, but something it expects.

As the specification of the HTTP/2 standard is finalized and approved, after going through some editorial processes HTTP/2 will be published and ready for adoption.

You may also like...