4 ms·
Intent to Remove: HTTP/2 and gQUIC server push
- jaffathecake 6y agoI think this is the right decision. I looked at HTTP/2 push in 2017 and the design is very confusing, and the implementations are pretty bad. https://jakearchibald.com/2017/h2-push-tougher-than-i-thought/ https://jakearchibald.com/2017/h2-push-tougher-than-i-though... Chrome's implementation was best, but the design of HTTP/2 push makes it really hard to do the right thing. Not just when it comes to pushing resources unnecessarily, but also delaying the delivery of higher priority resources. <link rel="preload"> is much simpler to understand and use, and can be optimised by the browser. Disclaimer: I work on the Chrome team, but I'm not on the networking team, and wasn't involved in this decision.