Published draft HTTP 2.0 specification
Today was published the draft specification of the standard HTTP / 2.0. HTTP 2.0 is the first new version of the HTTP protocol since the advent of HTTP 1.1, described in 1999 (RFC 2616).
Read the draft can be on the link: http://tools.ietf.org/html/draft-ietf-httpbis-http2-04
The main novelty: as the basis of HTTP / 2.0 SPDY is used - a binary application layer protocol from Google over a TCP / TLS connection.
HTTP / 2.0 is expected to preserve HTTP semantics, but avoiding the use of outdated syntax and message styling in the HTTP / 1.x style. Among the key tasks assigned to HTTP / 2.0:
As the basis of HTTP / 2.0 at the suggestion of Mark Nottingham, the head of the IETF working group, SPDY protocol is used, created by Google (it is already supported on Google, Twitter, Wordpress.com, Facebook, as well as in Chrome, Firefox, Opera and IE11 browsers) - thanks kirugan for additions). SPDY allows you to significantly speed up the loading of sites via HTTP by compressing HTTP headers, multiplexing requests, and prioritizing requests. It is designed specifically to minimize delays in connecting and exchanging data between the client and the server: according to Google itself, the acceleration of sites using it ranges from 15% to 50%. Protocol implementations 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. The code with the SPDY implementation is open under the Apache license.
')
On Habré, SPDY was discussed here a year ago.
Source code and bug tracker: https://github.com/http2/http2-spec
Wiki: http://tools.ietf.org/wg/httpbis/
Read the draft can be on the link: http://tools.ietf.org/html/draft-ietf-httpbis-http2-04
The main novelty: as the basis of HTTP / 2.0 SPDY is used - a binary application layer protocol from Google over a TCP / TLS connection.
HTTP / 2.0 is expected to preserve HTTP semantics, but avoiding the use of outdated syntax and message styling in the HTTP / 1.x style. Among the key tasks assigned to HTTP / 2.0:
- Improving the efficiency of using network resources (first of all - avoiding the need to create several TCP connections);
- Serious increase in performance for modern browsers and mobile devices;
- The ability to deploy in the modern Internet using IPv4 and IPv6, and not forgetting about NAT;
- Simplify the deployment of solutions based on HTTP;
- Providing modern security requirements;
- In the process of creating a specification, special attention is paid to the need to take into account the specific features of the HTTP application (for example, WebAPI and proxy).
As the basis of HTTP / 2.0 at the suggestion of Mark Nottingham, the head of the IETF working group, SPDY protocol is used, created by Google (it is already supported on Google, Twitter, Wordpress.com, Facebook, as well as in Chrome, Firefox, Opera and IE11 browsers) - thanks kirugan for additions). SPDY allows you to significantly speed up the loading of sites via HTTP by compressing HTTP headers, multiplexing requests, and prioritizing requests. It is designed specifically to minimize delays in connecting and exchanging data between the client and the server: according to Google itself, the acceleration of sites using it ranges from 15% to 50%. Protocol implementations 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. The code with the SPDY implementation is open under the Apache license.
')
On Habré, SPDY was discussed here a year ago.
Source code and bug tracker: https://github.com/http2/http2-spec
Wiki: http://tools.ietf.org/wg/httpbis/
Source: https://habr.com/ru/post/186102/
All Articles