Fair point, Ross. I suppose I was a bit too generic.

That said, I think the majority of website operators who don’t support
HTTP/3 could enable it relatively easily if there was a strong incentive.
Most major CDNs already support HTTP/3, but very few enable it by default.
Many self-hosted deployments could also gain support through an upgrade or
configuration change.

As you note, some platforms (like Apache httpd) still lack native support,
which is certainly a barrier. But even in those cases, operators have
options such as migrating to an alternative web server, or placing a CDN or
reverse proxy in front of their service. The real challenge is that, for
most operators, there simply isn’t a compelling reason to add that
complexity or take on migration risk.

Nginx has supported HTTP/3 for over two years now. It would be interesting
to know what proportion of nginx-based websites have actually upgraded to a
recent enough release and enabled HTTP/3. That data point could serve as a
useful indicator of the balance between technical capability and operator
inertia.


If I recall correctly, Google’s decision to factor TLS into PageRank
provided a strong incentive for websites to adopt encryption. Perhaps
HTTP/3 needs a similar kind of external driver to create new momentum?


Best Regards,
Yaroslav

On Mon, Sep 29, 2025 at 10:15 AM Ross Finlayson <[email protected]>
wrote:

> > 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).
>
>         Ross.
>
>

-- 


This communication (including any attachments) is intended for the sole 
use of the intended recipient and may contain confidential, non-public, 
and/or privileged material. Use, distribution, or reproduction of this 
communication by unintended recipients is not authorized. If you received 
this communication in error, please immediately notify the sender and then 
delete all copies of this communication from your system.

Reply via email to