Why does Cloudflare pull contents via HTTP/1.1?

[DGTL.ONE]

I wonder why Cloudflare does still connect to the origin server via HTTP/1.1 (according to the docs) and how I can benefit from HTTP/2 or HTTP/3 enabled when the origin connections use the old protocol in proxied mode?

As far as I understand the “behind the scenes” process, when a user is the first to visit a new uncached page he wouldn’t benefit from a real HTTP/2 or “Quic” connection since Cloudflare has to pull the contents synchronously from the origin via HTTP/1.1 first. So when I have a site with lots of contents and every user gets his own, dynamically generated image set, he would technically not recognise a better performance in comparison to HTTP/1.1 (when the images are not preloaded into Cloudflare’s cache from someone else in their nearby location).

Is this right or am I missing something? If so, wouldn’t it make sense for Cloudflare to also pull the contents via HTTP/2 or HTTP/3 when available on the origin?

[sdayman]

This comes up from time to time. From a Search, I found this:

HTTP/2 and origin server?

It appears that Cloudflare is not supporting HTTP/2 from the origin server. While reading this forum I read confirmation of this fact and the response is to use CF’s railgun product instead. Is the decision to not use HTTP/2 a technical design one or a business one to push users to use railgun? I am disappointed that H2 is not supported as It is clearly a faster experience in general. Perhaps its a feature that will come one day.