Hi,
On Mon, Sep 29, 2025, at 10:31, Stefan Eissing wrote: > > > > Am 29.09.2025 um 11:14 schrieb Ross Finlayson <[email protected]>: > > > >> 2. Website owners are reluctant to enable HTTP/3. > > > > Or website owners *cannot* enable HTTP/3. Remember that the Apache web > > server - which according to some statistics implements more than 25% of all > > websites - still does not support HTTP/3 (QUIC). > > No one has come forward to do or fund that development. Simple as that. > > Also, I doubt that it would have any influence on the cloudflare use numbers. > =) > > And, in addition, if one really wants that, there are several implementations > that can do HTTP/3 is a reverse proxy in front of any server. > > I would guess that many small web site owners simply do not care. And many > large site owners use a CDN, where all CDNs talk HTTP/1.1 to the origin host > exclusively because they have no HTTP/2 or HTTP/3 implementation in the > backend. I wonder why they think this is not worth it? FWIW Cloudflare speak HTTP/2 to origin by default now [1]. The capability to do so has been around a few years, I can't recall precisely when it was made default. Cheers Lucas [1] https://developers.cloudflare.com/speed/optimization/protocol/http2-to-origin/ > > So, I find that Apache argument not convincing. > > - Stefan >
