Monday, January 1, 2018

HTTP/2

HTTP/2 (originally named HTTP/2.0) is a major revision of the HTTP network protocol used by the World Wide Web. It was derived from the earlier experimental SPDY protocol, originally developed by Google.[1] HTTP/2[2] was developed by the Hypertext Transfer Protocol working group httpbis (where bis means "second") of the Internet Engineering Task Force.[3] HTTP/2 is the first new version of HTTP since HTTP 1.1, which was standardized in RFC 2068 in 1997. The Working Group presented HTTP/2 to IESG for consideration as a Proposed Standard in December 2014,[4][5] and IESG approved it to publish as Proposed Standard on February 17, 2015.[6][7] The HTTP/2 specification was published as RFC 7540 in May 2015.[8]
The standardization effort was supported by Chrome, Opera, Firefox,[9] Internet Explorer 11, Safari, Amazon Silk, and Edge browsers.[10] Most major browsers added HTTP/2 support by the end of 2015.[11]
According to W3Techs, as of November 2017, 20.5% of the top 10 million websites supported HTTP/2.[12]

Contents

Goals

The working group charter mentions several goals and issues of concern:[3]

Differences from HTTP 1.1

The proposed changes do not require any changes to how existing web applications work, but new applications can take advantage of new features for increased speed.[13]
HTTP/2 leaves most of HTTP 1.1's high-level syntax, such as methods, status codes, header fields, and URIs, the same. What is new is how the data is framed and transported between the client and the server.[13]
Websites that are efficient minimize the number of requests required to render an entire page by minifying (reducing the amount of code and packing smaller pieces of code into bundles, without reducing its ability to function) resources such as images and scripts. However, minification is not necessarily convenient nor efficient and may still require separate HTTP connections to get the page and the minified resources. HTTP/2 allows the server to "push" content, that is, to respond with data for more queries than the client requested. This allows the server to supply data it knows a web browser will need to render a web page, without waiting for the browser to examine the first response, and without the overhead of an additional request cycle.[14]
Additional performance improvements in the first draft of HTTP/2 (which was a copy of SPDY) come from multiplexing of requests and responses to avoid the head-of-line blocking problem in HTTP 1 (even when HTTP pipelining is used), header compression, and prioritization of requests.[15] HTTP/2 no longer supports HTTP 1.1's chunked transfer encoding mechanism, as it provides its own, more efficient, mechanisms for data streaming.[16]

Genesis in and later differences from SPDY

SPDY (pronounced like "speedy") was a previous HTTP-replacement protocol developed by a research project spearheaded by Google.[17] SPDY primarily focused on reducing latency. SPDY uses the same TCP pipe but different protocols to accomplish this reduction. The basic changes made to HTTP 1.1 to create SPDY included: "true request pipelining without FIFO restrictions, message framing mechanism to simplify client and server development, mandatory compression (including headers), priority scheduling, and even bi-directional communication".[18]
The httpbis working group considered Google's SPDY protocol, Microsoft's HTTP Speed+Mobility proposal (SPDY based),[17] and Network-Friendly HTTP Upgrade.[19] In July 2012 Facebook provided feedback on each of the proposals and recommended HTTP/2 be based on SPDY.[20] The initial draft of HTTP/2 was published in November 2012 and was based on a straight copy of SPDY.[21]
The biggest difference between HTTP/1.1 and SPDY was that each user action in SPDY is given a "stream ID", meaning there is a single TCP channel connecting the user to the server. SPDY split requests into either control or data, using a "simple to parse binary protocol with two types of frames".[18] SPDY showed evident improvement from HTTP, with a new page load speedup ranging from 11.81% to 47.7%.[22]
The development of HTTP/2 used SPDY as a jumping-off point. Among the many detailed differences between the protocols, the most notable is that HTTP/2 uses a fixed Huffman code-based header compression algorithm, instead of SPDY's dynamic stream-based compression. This helps to reduce the potential for compression oracle attacks on the protocol, such as the CRIME attack.
On February 9, 2015, Google announced plans to remove support for SPDY in Chrome in favor of support for HTTP/2.[23] That took effect, starting with Chrome 51.[24][25]

Encryption

HTTP/2 is defined for both HTTP URIs (i.e. without encryption) and for HTTPS URIs (over TLS using ALPN extension[26] where TLS 1.2 or newer is required).[27]
Although the standard itself does not require usage of encryption,[28] most client implementations (Firefox,[29] Chrome, Safari, Opera, IE, Edge) have stated that they will only support HTTP/2 over TLS, which makes encryption de facto mandatory.[30]

Criticisms

HTTP/2's development process and the protocol itself have faced criticism.
The FreeBSD and Varnish developer Poul-Henning Kamp claims that the standard was prepared on an unrealistically short schedule, ruling out any basis for the new HTTP/2 other than the SPDY protocol and resulting in other missed opportunities for improvement.[31] Kamp criticizes the protocol itself for being inconsistent and having needless, overwhelming complexity.[31] He also states that the protocol violates the protocol layering principle,[31] for example by duplicating flow control that belongs in the transport layer (TCP). Most concerns, however, have been related to encryption issues.

Encryption

Initially, some members[who?] of the Working Group tried to introduce an encryption requirement in the protocol. This faced criticism.
Critics stated that encryption has non-negligible computing costs and that many HTTP applications have actually no need for encryption and their providers have no desire to spend additional resources on it. Encryption proponents have stated that this encryption overhead is negligible in practice.[32] Poul-Henning Kamp has criticised IETF for following a particular political agenda with HTTP/2.[31][33][34] The criticism of the agenda of mandatory encryption within the existing certificate framework is not new, nor is it unique to members of the open-source community – a Cisco employee stated in 2013 that the present certificate model is not compatible with small devices like routers, because the present model requires not only annual enrollment and remission of non-trivial fees for each certificate, but must be continually repeated on an annual basis.[35] Working Group finally did not reach consensus over the mandatory encryption,[28] although most client implementations require it, which makes encryption a de facto requirement.
The HTTP/2 protocol also faced criticism for not supporting opportunistic encryption, a measure against passive monitoring similar to the STARTTLS mechanism that has long been available in other internet protocols like SMTP. Critics have stated that the HTTP/2 proposal goes in violation of IETF's own RFC7258 "Pervasive Monitoring Is an Attack", which also has a status of Best Current Practice 188.[36] RFC7258/BCP188 mandates that passive monitoring to be considered as an attack, and protocols designed by IETF should take steps to protect against passive monitoring (for example, through the use of opportunistic encryption). A number of specifications for opportunistic encryption of HTTP/2 have been provided,[37][38][39] of which draft-nottingham-http2-encryption was adopted as an official work item of the working group, leading to the publication of RFC 8164 in May 2017.

Development milestones

Status Date Milestone[3]
Done December 20, 2007[40][41] First HTTP 1.1 Revision Internet Draft
Done January 23, 2008[42] First HTTP Security Properties Internet Draft
Done Early 2012[43] Call for Proposals for HTTP 2.0
Done October 14 – November 25, 2012[44][45] Working Group Last Call for HTTP 1.1 Revision
Done November 28, 2012[46][47] First WG draft of HTTP 2.0, based upon draft-mbelshe-httpbis-spdy-00
Held/Eliminated
Working Group Last Call for HTTP Security Properties
Done September 2013[48][49] Submit HTTP 1.1 Revision to IESG for consideration as a Proposed Standard
Done February 12, 2014[50] IESG approved HTTP 1.1 Revision to publish as a Proposed Standard
Done June 6, 2014[40][51] Publish HTTP 1.1 Revision as RFC 7230, 7231, 7232, 7233, 7234, 7235
Done August 1, 2014 – September 1, 2014[5][52] Working Group Last call for HTTP/2
Done December 16, 2014[4] Submit HTTP/2 to IESG for consideration as a Proposed Standard
Done December 31, 2014 – January 14, 2015[53] IETF Last Call for HTTP/2
Done January 22, 2015[54] IESG telechat to review HTTP/2 as Proposed Standard
Done February 17, 2015[6] IESG approved HTTP/2 to publish as Proposed Standard
Done May 14, 2015[55] Publish HTTP/2 as RFC 7540

Server-side support

Main article: Comparison of web server software

Server software

Content delivery networks

  • Akamai is the first major CDN to support HTTP/2 and HTTP/2 Server Push. http2.akamai.com showcases Akamai's HTTP/2 implementation, including Server Push.
  • CDN77 supports HTTP/2 using nginx (August 20, 2015). http2demo.io is a demonstration of CDN77's HTTP/2 implementation.
  • Cloudflare supports HTTP/2 using nginx with SPDY as a fallback for browsers without support, whilst maintaining all security and performance services.[78] Cloudflare was the first major CDN to support HTTP/2 Server Push.[79]
  • AWS CloudFront supports HTTP/2.[80]
  • Fastly supports HTTP/2 including Server Push.[81]
  • Imperva Incapsula CDN supports HTTP/2.[82] http2.incapsula.com showcases Incapsula's HTTP/2 implementation. The implementation includes support for WAF and DDoS mitigation features as well.
  • KeyCDN supports HTTP/2 using nginx (October 6, 2015). HTTP/2 Test is a test page to verify if your server supports HTTP/2.

Not planned

  • lighttpd has no support for SPDY[83] and HTTP/2 might come in version 1.5.[84]

Implementations

Posted by at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)