HTTP/2 finished, coming to browsers within weeks

The Internet Engineering Task Force's HTTP Working Group has finalized its work on Hypertext Transfer Protocol 2, the successor to the HTTP/1.0 and HTTP/1.1 protocols that are the core of the Web.

The working group has actually finalized two closely related specifications. The first is HTTP/2 itself. The second is called HPACK, a specification for compressing HTTP/2 headers.

Work on HTTP/2 began in 2012 in response to the development of Google's SPDY protocol. Google created SPDY to address a number of performance gripes that the company had with traditional HTTP.

Perhaps the biggest issue with HTTP/1.x was its use of multiple connections to load resources in parallel. While a single HTTP/1.x connection between a client and a server can be used to request multiple different objects (the images, CSS, and JavaScript that an HTML page may require), those objects have to be served up in order, one after the other. If one object takes a long time, perhaps because it's very large or perhaps because it requires a lot of server time to create, then all the other objects requested subsequently have to wait.

As a result, most HTTP/1.x connections are used to request just a single object. Web clients do perform parallel loading of the objects that they need, but they do so by creating multiple connections to each server. But this has a cost of its own: it uses up additional network resources, and it takes extra time, with each individual connection requiring several transfers from client to server and back again.

HTTP/2 directly addresses this issue. In HTTP/2, multiple bidirectional streams are multiplexed over a single TCP connection. Each stream can carry a request/response pair, and multiple requests to a server can be made by using multiple streams. However, the streams are all independent; if one stream is slow, the HTTP/2 connection can still be used to transfer data belonging to other streams. Similarly, a client can request a large object and then a small object, and the response to the small object can be given before, or even during, the response to the large object. The waiting and sequential processing that are a feature of HTTP/1.x aren't needed in HTTP/2. The specification recommends that clients and servers support at least 100 different streams over a single connection.

HTTP/2 also brings some other changes to improve performance and capabilities. Traditional HTTP/1.x is a text protocol, with requests and responses all using plain human-readable text. HTTP/2 is a binary protocol that splits requests and responses into sequences of non-human-readable frames that are transmitted over the TCP connection. HTTP/2 also allows servers to push streams to clients without those clients having to make the initial request.

While a binary protocol, HTTP/2 doesn't change the underlying semantics of an HTTP connection. Requests and responses are still divided between headers and (optionally) bodies, with the headers used to provide important metadata about the bodies. Rather, the protocol is a new way of expressing those same messages designed to make HTTP communication more efficient.

HTTP/2 is based in large part on Google's SPDY. SPDY did some things that HTTP/2 does not. It required the use of TLS (Transport Layer Security) to enhance privacy and security. HTTP/2 makes this optional; it can operate over TLS or over plain TCP. Some vendors, however, have said that their implementations will only support HTTP/2 over encrypted TLS connections to regain these privacy benefits.

SPDY also—initially—used gzip compression for the headers sent in both directions. In 2012, however, this use of gzip was discovered to be dangerous, exposing users to an attack that has become known as CRIME. SPDY was altered to stop using gzip in this way. HTTP/2's solution is that second specification: HPACK.

HPACK is a way of compressing the HTTP headers sent over HTTP/2 connections that avoids the CRIME flaw. Unlike gzip, which is a general purpose compression algorithm, HPACK is designed specifically for HTTP/2's needs.

With IETF signing off on HTTP/2, the next steps are for some editing to be done and for both HTTP/2 and HPACK to be officially published as RFCs.

Browsers are well on their way toward supporting the new specification. Chrome 40 will include HTTP/2 support, with Google announcing earlier this month that SPDY support would be removed from Chrome in early 2016. Mozilla has said that Firefox 36, due to be released next week, will negotiate HTTP/2 connections using drafts 14 and 15 of the specification. Firefox 37 and 38 will add draft 16. The finalized version, draft 17, should follow soon after. The Windows 10 Technical Preview also includes support for draft 14, and the Project Spartan browser that's replacing Internet Explorer will include HTTP/2 support.

千里马比喻什么样的人	狗肉和什么食物相克	甲亢吃什么食物好	什么什么的荷叶	cj是什么意思
dcdc是什么意思	云南白药有什么功效	小孩为什么会得手足口病	跳蚤长什么样子图片	吃什么水果降火最快
宝宝说话晚是什么原因造成的	凯撒沙拉酱是什么口味	太傅是什么官	夏天做什么菜	场面是什么意思
红茶加枸杞有什么功效	呵护是什么意思	伤骨头了吃什么好得快	脱发应该挂什么科室	为什么尿频

减肥有什么好方法hcv9jop3ns5r.cn	刮宫是什么kuyehao.com	22年属什么生肖0297y7.com	阴道骚痒是什么原因hcv8jop3ns4r.cn	lime是什么颜色hcv9jop3ns0r.cn
冲锋衣三合一是什么意思hcv9jop6ns1r.cn	猎奇是什么意思hcv8jop9ns7r.cn	嘴唇上长水泡是什么原因hcv9jop8ns3r.cn	虚张声势是什么生肖hcv8jop5ns8r.cn	梦见楼塌了是什么意思hcv8jop5ns7r.cn
弱水三千只取一瓢什么意思hcv9jop3ns6r.cn	第二磨牙什么时候长hcv8jop5ns9r.cn	经常便秘吃什么调理hcv9jop2ns5r.cn	松子吃多了有什么害处hcv8jop0ns9r.cn	醉酒第二天吃什么才能缓解难受hcv7jop6ns0r.cn
九月十四号是什么星座clwhiglsz.com	骇人是什么意思hcv8jop6ns6r.cn	脂肪肝用什么药物治疗hcv8jop5ns1r.cn	风湿和类风湿有什么区别hcv8jop5ns2r.cn	低烧不退是什么原因hcv9jop3ns1r.cn