HTTP/2 Server Push
The cluster focuses on HTTP/2 server push, including explanations of how it works, its advantages for proactive resource delivery, deprecation status, browser support issues, and comparisons to alternatives like WebSockets or early hints.
Activity Over Time
Top Contributors
Keywords
Sample Comments
It's coming. That's what HTTP/2 PUSH is for.
How would server push from a web server work?
Sounds a lot like HTTP/2 push.
I think you are speaking about HTTP push, which has been abandoned [1] (also discussed in HN [2]).[1] https://evertpot.com/http-2-push-is-dead/[2] https://news.ycombinator.com/item?id=25283971
No mention of server push, so I assume it's not supported?
http2 has push, so you can make a single request (for the friends of a user) and then just push all the users in that response before the client requests it. this all happens over a single connection and leverages all the http infrastructure and experience you already have
Except when one uses server push and that's not true anymore.
Can somebody explain in simple words what HTTP/2 push means? Example?
That is one of the main advantages of HTTP2 - it's called server push. When the server receives a request, it can send the headers for the requested resource plus the headers for as many related resources as it wants. The client can choose to either disable this, or reject pushed streams when it receives their headers.
It's interesting that http2 server push is not supported. Any reason why? Server push is a weird feature but very useful and popular.