4 ms·
HTTP/2 Server Push is dead, and Chromium dropped support in 106: https://developer.chrome.com/blog/removing-push/ https://developer.chrome.com/blog/removing-pus
by callahad 3y ago
HTTP/2 Server Push is dead, and Chromium dropped support in 106: https://developer.chrome.com/blog/removing-push/ https://developer.chrome.com/blog/removing-push/
- azangru 3y agoThere are early hints instead [0]. Aren't they sort of a replacement for http2 push? [0] - https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/103 https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/103
- aseipp 3y agoThe intended purpose of both Server Push and Early Hints is basically "Lower overall latency by letting the client know early on that there is more data it might need in subsequent requests." But in practice Early Hints are much better because only the client knows definitively if it needs the resource or not i.e. a 103 might say "you might need this file soon" but you already have it in cache. Both approaches would still require the server to have some knowledge about the semantic request/response structure of client applications, though.