HTTP 2.0 First Draft Published

| by Dio Synodinos Follow 3 Followers on Nov 30, 2012. Estimated reading time: 1 minute |

A note to our readers: You asked so we have developed a set of features that allow you to reduce the noise: you can get email and web notifications for topics you are interested in. Learn more about our new features.

The editors of the HTTP specification have published an initial draft of v2 which is a straight copy of SPDY and will be used as a base for diffs going forward. Many changes are expected to be done like adding new features, removing existing ones, changing the bytes on the wire, etc. A draft ready for test implementations is expected to be published early next year.

HTTP 2.0 is being developed by the Hypertext Transfer Protocol Bis (httpbis) working group of the IETF and will be the first new version since v1.1  (RFC 2616) in 1999.

Goals for HTTP 2.0 include:

  • Asynchronous connection multiplexing,
  • Header compression, and
  • Request-response pipelining.

Key goal is also to maintaining backwards compatibility with the semantics of HTTP 1.1.

SPDY is an HTTP compatible protocol launched by Google and supported in Chrome, Opera, Firefox, and Amazon Silk browsers.

One of the bottlenecks of HTTP implementations is that HTTP relies on multiple connections for concurrency. HTTP pipelining can help, but only achieves partial multiplexing.  In addition, pipelining has proven non-deployable in existing browsers due to intermediary interference.

SPDY adds a framing layer for multiplexing multiple, concurrent streams across a single connection. That layer is optimized for HTTP-like request-response streams, similar to what is used by modern web apps.

SPDY offers four improvements over the current version of HTTP:

  • Multiplexed requests
  • Prioritized requests
  • Compressed headers
  • Server pushed streams (server push)

SPDY attempts to preserve the existing semantics of HTTP, so features like cookies, ETags, etc are available.

Many of the architectural approaches in SPDY (e.g. multiplexing), were explored earlier by W3C’s HTTP-NG working group which was suspended in 1998. Improving HTTP has been an issue of discussions for many years and it has even been the subject of InfoQ’s April Fools’ joke a while ago.

Rate this Article

Adoption Stage

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


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

Recover your password...


Follow your favorite topics and editors

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


More signal, less noise

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


Stay up-to-date

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