July 9, 2013 at 20:00Draft HTTP 2.0 specification published
Today, a draft draft specification of the HTTP / 2.0 standard was published. HTTP 2.0 is the first new version of the HTTP protocol since the advent of HTTP 1.1, described in 1999 (RFC 2616).
You can read the draft here: http://tools.ietf.org/html/draft-ietf-httpbis-http2-04
Main novelty: SPDY is used as the basis for HTTP / 2.0 - Google’s binary application layer protocol over TCP / TLS connection .
In HTTP / 2.0, the semantics of HTTP are expected to be preserved, but the avoidance of using obsolete syntax and message design in the style of HTTP / 1.x. Among the key tasks entrusted to HTTP / 2.0:
Based on the proposal of Mark Nottingham, the head of the IETF working group, HTTP / 2.0 uses the SPDY protocol created by Google (it is already supported on Google, Twitter, Wordpress.com, Facebook, and also in Chrome, Firefox, Opera, and IE11 - thanks kiruganfor additions). SPDY can significantly accelerate the loading of sites via HTTP due to compression of HTTP headers, multiplexing of requests and prioritization of requests. It is designed specifically to minimize delays in connecting and exchanging data between the client and server: according to Google itself, the speed of sites using it ranges from 15% to 50%. Implementations of the protocol are available in Python, Go, Ruby, Java, and JavaScript (node.js). A special proxy server has been prepared that allows using the SPDY protocol for any sites. SPDY implementation code is open source under the Apache license.
On Habré SPDY a year ago was discussed here .
Source code and bug tracker: https://github.com/http2/http2-spec
Wiki:http://tools.ietf.org/wg/httpbis/
You can read the draft here: http://tools.ietf.org/html/draft-ietf-httpbis-http2-04
Main novelty: SPDY is used as the basis for HTTP / 2.0 - Google’s binary application layer protocol over TCP / TLS connection .
In HTTP / 2.0, the semantics of HTTP are expected to be preserved, but the avoidance of using obsolete syntax and message design in the style of HTTP / 1.x. Among the key tasks entrusted to HTTP / 2.0:
- Improving the efficiency of using network resources (first of all, avoiding the need to create several TCP connections);
- A significant increase in performance for modern browsers and mobile devices;
- The ability to deploy on the modern Internet using IPv4 and IPv6, and not forgetting about NAT;
- Simplify the deployment of HTTP-based solutions;
- Ensuring modern security requirements;
- In the process of creating the specification, special attention is paid to the need to take into account the specific features of the use of HTTP (for example, WebAPI and proxies).
Based on the proposal of Mark Nottingham, the head of the IETF working group, HTTP / 2.0 uses the SPDY protocol created by Google (it is already supported on Google, Twitter, Wordpress.com, Facebook, and also in Chrome, Firefox, Opera, and IE11 - thanks kiruganfor additions). SPDY can significantly accelerate the loading of sites via HTTP due to compression of HTTP headers, multiplexing of requests and prioritization of requests. It is designed specifically to minimize delays in connecting and exchanging data between the client and server: according to Google itself, the speed of sites using it ranges from 15% to 50%. Implementations of the protocol are available in Python, Go, Ruby, Java, and JavaScript (node.js). A special proxy server has been prepared that allows using the SPDY protocol for any sites. SPDY implementation code is open source under the Apache license.
On Habré SPDY a year ago was discussed here .
Source code and bug tracker: https://github.com/http2/http2-spec
Wiki:http://tools.ietf.org/wg/httpbis/