BT

New Early adopter or innovator? InfoQ has been working on some new features for you. Learn more

Google Dumps SPDY after HTTP/2 Enters "Last Call"

| by Abel Avram Follow 4 Followers on Feb 10, 2015. Estimated reading time: 2 minutes |

Google has announced giving up SPDY after HTTP/2.0 has integrated the protocol and its standardization is in its final stages.

The Internet has run mostly on HTTP/1.1 since its standardization in 1999 as RFC 2616, a protocol that was later updated or made obsolete by 10 other newer versions of the standard. But some considered that there was room for improvement especially regarding its performance. Google was one of them, announcing the SPDY protocol back in 2009. Usually such an attempt has few chances to succeed because of the vastness of the Internet, but Google had one weapon to make it work: Chrome. They made their own websites and Chrome support SPDY, enticing users with better performance and putting pressure on other browser makers and websites.

Currently, SPDY is used by 3.4% of over 1.2B websites worldwide, according to W3Techs, which is not an important percentage, but among those are some of the largest websites including Google, Facebook, Yahoo!, Twitter, YouTube, Wordpress, etc., making the number of pages served daily over SPDY an important share of all pages.

The IETF HTTPBIS Working Group responsible for the standardization of HTTP/2.0 made SPDY a starting point for a discussion back in 2012, but initially they did not intend to fully adopt it. Microsoft had their own proposal called HTTP Speed+Mobility. Three years later it turns out that SPDY has won and it has been adopted by the HTTPBis WG for HTTP/2.0, being in the “Last Call” status in the standardization process.

As a result, Google has announced the retirement of SPDY by early 2016, implementing instead HTTP/2.0. It’s more of a name change for Google websites and Chrome rather than a protocol change. The latest Chrome 40 has a SPDY/4 flag that can be enabled by those interested in testing HTTP/2.0. Google is also removing support for NPN in favor of ALPN in Chrome, suggesting developers to use the latest TLS extension.

HTTP/2.0 is currently working with or without flags in Firefox, Chrome, Safari, Opera, iOS Safari, Chrome for Android, and IE 11 on Windows 8, according to CanIUse. The Windows 10 Preview also has it enabled in its browsers. Apache, IIS on Windows 10, and nginx have implemented SPDY 3.1 or 4 (HTTP/2.0). It remains for website admins to upgrade their servers.

Rate this Article

Adoption Stage
Style

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread
Community comments

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Discuss

Login to InfoQ to interact with what matters most to you.


Recover your password...

Follow

Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.

Like

More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.

Notifications

Stay up-to-date

Set up your notifications and don't miss out on content that matters to you

BT