Modernizing the Web: HTTP/2 currently available for VPS and Dedicated Servers

Posted on

The Internet is a touch of a categorization with reference to however it evolves. New technologies appear to pop, grow, and expand virtually on a everyday, nevertheless the underlying protocol that powers the net as we all know it saw (until recently) virtually no significant growth for nearly fifteen years. The machine-readable text Transfer Protocol (HTTP) was originally designed by Tim Berners-Lee within the late Nineteen Eighties, and also the last vital retread of the protocol was wiped out 1999 (standardized as associate degree RFC that was free after I was in second grade). Last year, a serious retread of communications protocol was finalized within the sort of HTTP/2, a serious upgrade to the underlying backbone of the net as we all know it nowadays.

Why Update HTTP?

The developers of the communications protocol/2 description have provided a superb outline on why and the way HTTP was improved within the latest protocol description. In short, HTTP/1.1 was designed for a distinct time, once websites were smaller, simpler, and cheaper to send across the wire. The explosive growth of the net within the last decade has seen a paradigm shift in however website and applications area unit designed and deployed. Websites and internet applications use larger, a lot of advanced media assets, and serve a lot of content than ever—and there’s no sign of this retardation down. The workarounds place in situ by developers and engineers to induce around a number of the inherent limitations of HTTP/1.1 (like request pipelining, domain sharding, etc.) were hacks and bandaids that were ne’er self-addressed at a basic level, and stood for the most part in distinction to a number of the planning options of transmission control protocol, the underlying communication protocol that communications protocol lives on. HTTP/2 was designed to require under consideration the character of the fashionable internet, providing associate degree economical customary for contemporary servers and shoppers to speak over.

HTTP/2 brings variety of latest options to the table, including:

A binary protocol, creating it a lot of compact to ship over the wire

Fully multiplexed, parallel connections give quicker, a lot of economical knowledge transfer

Server push practicality, enable internet designers to make sites that proactively send assets which will be required by an online page

Industry Adoption

Shiny options and well-designed protocols area unit all well and sensible, however they’re good-for-naught while not really getting used. when windup in mid-2015, the HTTP/2 protocol shortly saw early adoption from service suppliers like Akamai, Google, and Facebook, ASCII text file communications protocol servers like Nginx, and browsers, as well as Chrome, Firefox, Safari, and even net mortal (shocker, I know). consistent with researchers trailing the adoption rate of HTTP/2, nearly 200,000 sites from the Alexa list of high one thousand thousand websites announce support for HTTP/2.

Securing HTTP/2

As the successor to the SPDY protocol, several early adopters expected HTTP/2 to need a TLS affiliation, even as its forerunner did. Ultimately it absolutely was determined by the protocol’s designers that secure connections wouldn’t be required; but, that hasn’t forestall browser developers to need encoding. presently no browser implementations support plaintext HTTP/2 connections (also referred to as h2c).

HTTP/2 servers use one among 2 negotiation protocols to announce their support via TLS connections: NPN and ALPN. NPN is associate degree older, less-efficient negotiation protocol, whereas ALPN is newer, faster, and has seen a lot of less adoption because of its exclusion from older OpenSSL builds. curiously, Google has proclaimed plans for Chrome to drop support for NPN in exclusive favor of ALPN, that might leave several users within the HTTP/2 dark whereas heritage OpenSSL packages still float around.

HTTP/2 at DreamHost

As a supplier dedicated to clutches open supply comes, we’ve with excitement determined to hotfoot with adoption of HTTP/2. beginning in the week, domains hosted on VPS and dedicated servers steam-powered by Nginx will currently take full advantage of the HTTP/2 protocol. HTTP/2 support in Nginx is meant to figure seamlessly aboard existing HTTP/1.1 connections, albeit just for HTTPS sites. different existing options provided by our Nginx services, as well as additional internet security and Lua support via OpenResty, also will still work transparently beneath HTTP/2.

Additionally, DreamHost-powered HTTP/2 servers area unit absolutely capable of supporting each NPN and ALPN negotiations, that means Chrome’s close at hand cutoff for NPN won’t lead to affiliation errors on bleeding-edge browsers.

Adding HTTP/2 support to your Nginx/HTTPS domain is as straightforward as activating a checkbox. read the content article for any details and directions on the way to activate this service.

HTTP/2 DreamHost panel

And for the extra-curious, there area unit variety of wonderful resources concerning HTTP/2 that cut into a lot of deeper into the nitty gritty:

The HTTP/2 listing

The HTTP/2 RFC

HTTP/2 Adoption Matrix

2 thoughts on “Modernizing the Web: HTTP/2 currently available for VPS and Dedicated Servers

Leave a Reply

Your email address will not be published.