HTTP/2: the Future of the Internet

HTTP/2[1] is about to get very real. The standard has just been finalized, leading browsers are beginning to support it and so is Akamai. But why is this important?

HTTP Timeline

The web has dramatically evolved over the last 20+ years, yet HTTP - the workhorse of the Web - has not. Web developers have worked around HTTP's limitations, but: HTTP/2 attempts to solve many of the shortcomings and inflexibilities of HTTP/1.1.

Its many benefits include:

You will not need to change your websites or applications to ensure they continue to work properly. Not only will your application code and HTTP APIs continue to work uninterrupted, but your application will also likely perform better and consume fewer resources on both client and server.

As it becomes more prevalent, organizations looking to benefit from the performance and security features of HTTP/2 should start thinking about how they are invested to fully capitalize on these new capabilities. Such considerations include:

Akamai can help and is working hard to address these and additional challenges, including possibly the toughest one: optimizing differently for HTTP/1.1 vs. HTTP/2 connections as browsers and other clients gradually transition over the next several years.

Akamai supports HTTP/2 in limited beta and is working hard to broaden availability to additional customers. Akamai's Mark Nottingham chairs the IETF working group that defined the new standard - demonstrating our commitment to benefit users, content providers, service providers, developers and the Internet community at large

For a preview of how your website or application is likely to perform on HTTP/2 once it is widely supported, you can experiment on the Akamai platform with SPDY/3.1. It is important to note that Akamai and leading browsers intend to stop supporting SPDY when HTTP/2 is ready to take its place.

For questions, please reach out to your Akamai representative, visit the Akamai Community or click here to contact us.

1. Formerly know as HTTP/2.0 or HTTP 2.0