Related to THIS article HTTP/3 should also be able to use “Server Push”.
But when I download the latest Chrome Canary build and activate HTTP/3 then I can not receive a Push from any CloudFlare site. Specially not mine.
So I made some screenshots to provide a bit more infos and some pics.
Now this can maybe be related to Chrome Canary, but as I’m not sure where this is not “implemented” I just want to create this Thread and maybe some of the devs can have a look at it or state why Push is not working with HTTP/3.
As soon as I switch to HTTP/3 no Initiator will show “Push / Other”. Also nothing gets pushed what you can see at the waterfall diagram.
I haven’t dug deep on this, but do the headers show anything? As I recall, the server sends the Link: header, then Cloudlfare pushes it and sends some sort of cf-push header instead of the Link: header.
Yeah, but the original linked article talks about HTTP/2 & 3, then Server Push. It gives the impression that HTTP/2 is great, but HTTP/3 is even better. And you can do Server Push! Logically, it doesn’t make sense to lose a good feature when moving up a level.