What is HTTP 2.0 and What Changes will it bring?

HTTP is that the protocol designed by the IETF and W3C to control transactions of data (files, database queries, etc.) on theWorld Wide Web, once 18 years since the implementation of protocol 1.0 by Tim himself Berners-Lee, a similar version 2.0 is about to reach our browsing sessions (the forecast is that this happens from November 2014).

The current HTTP 1.1 protocol dates back to 1999, a time once web technologies we have radically completely different than those we use these days (without going further: multimedia traffic was anecdotal, and mobile) and it absolutely was not possible to imagine the amount of traffic that moves the WWW these days. Therefore, in 2009 Google announced it absolutely was engaged on a new HTTP protocol support, however would improve safety and efficiency (intended to realize a discount in load time of pages of a minimum of 50%). His name was SPDY (pronounced ‘speedy’), and shortly made public, the HTTPbis Working Group of the IETF decided set to use it because the basis for the new version of HTTP in which they were working.

Among the changes introduced and wont to improve the efficiency of Web communications.

  • Compressing HTTP headers, that considerably limit the amount of data transmitted.
  • Sending cookies only happens if its value has modified with reference to your last shipment.
  • Multiplexing HTTP requests on a similar TCP connection (Google is additionally conducting tests with another proprietary protocol referred to as QUIC, that performs this multiplexing connections over UDP rather than TCP, therefore speeding up futhure navigation).
  • Support for ‘server push’ (which will force a server sending data to the client while not this the software requested, so saved a connection).
  • All this translates into lower consumption of bandwidth, lower data overload and quicker loading of website.

With reference to security, the main change is that the necessary use of SSL with HTTP 2.0 connections. This decision seems to be motivated by the ‘Scandal Snowden’ on-line spying the NSA intelligence agency. As indicated by the HTTP 2.0 project leader, Mark Nottingham, it was felt that the only way to improve overall web security was forced to use HTTPS url’s that doesn’t mean that traditional non-secure HTTP to go away : simply they still perform under version 1.1 of the protocol.