HTTP/2’s primary changes from HTTP/1.1 focus on improved performance. Some key features such as multiplexing, header compression, prioritization and protocol negotiation evolved from work done in an earlier open, but non-standard protocol named SPDY. Chrome has supported SPDY since Chrome 6, but since most of the benefits are present in HTTP/2, it’s time to say goodbye. We plan to remove support for SPDY in early 2016, and to also remove support for the TLS extension named NPN in favor of ALPN in Chrome at the same time. Server developers are strongly encouraged to move to HTTP/2 and ALPN.
We’re happy to have contributed to the open standards process that led to HTTP/2, and hope to see wide adoption given the broad industry engagement on standardization and implementation. We also look forward to further advancements in fundamental Internet protocols that lead to a faster and more secure Internet for everyone.
Update: Beginning May 15, Chrome will no longer support SPDY. Update: To better align with Chrome's release cycle, SPDY and NPN support will be removed with the release of Chrome 51.
Posted by Chris Bentzel, Multiplexing Manager and Bence Béky, HTTP/2 Enabler
