HTTP/3 + QUIC usage on HTTP/1.1 Origin

Hey together,

i haven´t found any documentation on how Cloudflare uses their http/3+quic protocol on cloudflare tunnel applications.

For example:
Browser — Cloudflare ---- CloudflareD(locally) ----- Local HTTPS Endpoint

The Endpoint has HTTP1.1. Is Cloudflare Tunnel using http/3 only between Browser and Cloudflare or also between Cloudflare and CloudflareD and the conversion to http1.1 is done by CloudflareD locally?

Another Scenario is also interesting because we want to use it in the very near future:
Browser — Cloudflare ----- Cloudflare Load Balancer ---- CloudflareD(locally) ----- Local HTTPS Endpoint

On which Connection Paths Cloudflare will use http/3?

I’m also interested in this issue.

However, if there is a tutorial on installing http3 on centos7 + php 8.2 with nginx that would be great. I am optimizing one of my pages https://vnetglobal.vn/dich-thuat-tieng-anh/ and have followed a few tutorials found on google but it shows an error. but when checking the header it still shows H3. Why is this? whether it worked or not. Does anyone have suggestions for this?

All comments are appreciated

Do you want Cloudflare Proxy to talk to your origin with HTTP/3?

I only know the official way: Support for QUIC and HTTP/3
But it is still in Beta stage. So I won´t do that in production environment.