HTTP/2 finally arriving!

[Nylanfs]

https://gizmodo.com/second-coming-the-first-http-update-in-16-years-http-1686479223?utm_campaign=socialflow_gizmodo_faceboo k&utm_source=gizmodo_facebook&utm_medium=socialflow

[damned]

most web servers dont support multiple ssl sites/certs sharing a single ip address and resolving using host headers. this will need to be resolved if they want everyone running http/2 in SSL...


https://www.fg-con.com/wp-content/uploads/2015/01/fg-con-6-150-3.jpg (https://www.fg-con.com/events/)
FG Con 6 – April 17-19th 2015 - register at www.fg-con.com (https://www.fg-con.com/) for all the latest info.

[darrenan]

HTTP/2 is mainly about using the TCP pipe more efficiently by adding streams. The issue you cite, while valid, is completely orthogonal. The issues you cite are handled at the TLS layer, which sits below HTTP (except for specifying protocol during the TLS handshake). I would not expect to see these issues solved by a new HTTP protocol as they are mostly unrelated.

The main issues around HTTP/2 adoption will be how quickly can the existing HTTP stacks be upgraded to support HTTP/2, on both the client and server sides. It sounds like Google is going to be moving on this pretty quickly in Chrome, but web site adoption will depend on adding HTTP/2 capabilities to existing server stack architectures.

[damned]

absolutely independent of each other - understood - except that the majority of the companies/organisations driving http/2 are also pushing for everything on the web to use secure connections.