Aug 5, 2026, 7:44 AMAnyone using HTTP/2 server push with libcurl?
If you use this feature in libcurl, please let us know. It is being deprecated all over, including in specs, browsers and servers and I believe the time has come for us to drop it from libcurl in the future as well.
So I'm curious to know if anyone actually (still) uses it.
@bagder I have it as a fundamental part of a design, that has not been implemented. That design prefers HTTP3 though; do you know if you'd also be removing HTTP3 server push support?
For HTTP2 there's a big design flaw in it so I'm much less likely to use it.
Aug 5, 2026, 8:35 AM@dascandy HTTP/3 has no server push! It had already been deemed a failure by then ...
@bagder Am I misreading chapter 4.6, "Server Push", in RFC 9114 ? https://www.rfc-editor.org/rfc/rfc9114.html#name-server-push
Aug 5, 2026, 8:37 AM@dascandy hm, I must be misremembering things, sorry. I don't think anyone anywhere implements it though. libcurl does not support it for h3.
@bagder iirc the big problem was that it's nearly always just adding overhead, and in case of HTTP2 doing Head-Of-Line blocking too, making it a net negative in almost all cases. In HTTP3 they fixed the HOL blocking, but it's still only useful if there is something the client wants, cannot know that it should request, and is very urgent / time-dependent to the point of needing a few RTTs saved. Which for regular web servers is extremely close to nothing... and arguably you could always have an active websocket on a channel in http2 or 3 that does exactly what your push would do to accomplish the same.
Aug 5, 2026, 8:56 AM@dascandy yes, that's what everyone learnt why sever push is going away everywhere.
Aug 5, 2026, 8:59 PM