Quirky work-arounds Annoying for developers Adds layers of tools Hampers caching Downloads too much
“Just a new framing layer” maintains HTTP paradigms http:// and https:// URLs cannot be changed HTTP/1.1 servers and clients wil be around for decades Proxies must be able to convert 1:1 Less optional parts No more minor version!
HTTP/2 framing Binary Multiplexed streams; with individual priorities, dependencies and flow-control Header compression Server push
HTTP/2 is not Mandatory TLS Changing HTTP headers
How will HTTP/2 affect web users? Faster page loads More responsive loading
How will HTTP/2 affect web development? HTTP/1 work-arounds hurt HTTP/2 perf Need to do separate tweaks Maximum HTTP/2 usage wil need some time
Will HTTP/2 get widely deployed? “Look at IPv6” SPDY proved fast growth can happen Major browsers are on the train Many sites already did SPDY - likely to go HTTP/2
How will HTTP/2 affect web development? HTTP/1 work-arounds hurt http2 perf Need to do separate tweaks Maximum HTTP/2 usage wil need some time
HTTP/2 – Status of February 1st 2015 Firefox: HTTP/2 in 9% of all HTTP responses1 HTTP/2 is used 9 times more than HTTP/1.0 Google: HTTP/2 used in 5% of global traffic2 IPv6: 5% today, almost 20 years after first RFC 1. Rough and not statistically sound numbers from Mozil a Telemetry data for Firefox 35. 2. Rough and rapidly changing numbers in an evolving climate. Graciously provided by Google.
Schedule IETF Last Cal ended on January 14th Firefox 35 – enabled by default January 13th Chrome 40 – enabled by default January 21st HTTP/2 final RFC in Q1 2015 ?
HTTP/3 ? HTTP/2 lays the foundation for the future Time to drop legacy HTTP “mistakes”? HTTP/3 can happen sooner than the 1.1 to 2 took