We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

So that was HTTP/2, what's next?

2
 Cite
 Share
 Download
 Purchase
Logo of FOSDEM VZWFOSDEM VZW
 Stenberg, Daniel

Formal Metadata

Title
So that was HTTP/2, what's next?
Title of Series
Number of Parts
611
Author
License
CC Attribution 2.0 Belgium:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language
Production Year2017

Content Metadata

Subject Area
Genre
Abstract
A look at how HTTP/2 has improved the web, which cases that are stillproblematic and what's being done about it next. Will there be a QUIC fix? A recap on what HTTP/2 brought that HTTP/1 couldn't offer before we dig in andlook at some numbers that show how HTTP/2 has improved (browser) networkingand the web experience for people. Still, there are scenarios where HTTP/1's multiple connections win over HTTP/2in performance tests. Why is that and what is being done about it? Wasn'tHTTP/2 supposed to be the silver bullet? A closer look at QUIC, its promises to fix the areas where HTTP/2 didn'tdeliver and a check on where it is today. Is QUIC perhaps actually HTTP/3 ineverything but the name? Depending on what exactly happens in this area over time until FOSDEM, I willspice it up with more details on how we work on these protocol things inMozilla/Firefox!