# HTTP/3 adoption is widespread in browsers and CDNs but limited in open-source tools

DevFeed: [HTTP/3 adoption is widespread in browsers and CDNs but limited in open-source tools](<https://devfeed.tech/articles/http-3-is-everywhere-but-nowhere-19074.md>)

Original publisher: [Read original article](<https://httptoolkit.com/blog/http3-quic-open-source-support-nowhere/>)

Author: HTTP Toolkit; Tim Perry

Published: 2025-03-12T16:00:00Z

Content type: opinion

Language: en

Sources: [HTTP Toolkit](<https://devfeed.tech/sources/http-toolkit.md>)

Topics: [HTTP3](<https://devfeed.tech/topics/http3.md>), [networking](<https://devfeed.tech/topics/networking.md>), [Protocol (disambiguation)](<https://devfeed.tech/topics/protocol.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [browsers](<https://devfeed.tech/tags/browsers.md>), [http](<https://devfeed.tech/tags/http.md>), [http-3](<https://devfeed.tech/tags/http-3.md>), [http3](<https://devfeed.tech/tags/http3.md>), [networking](<https://devfeed.tech/tags/networking.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [quic](<https://devfeed.tech/tags/quic.md>), [standards](<https://devfeed.tech/tags/standards.md>)

## AI overview

This article examines the contrast between HTTP/3's widespread browser and CDN adoption and its limited support in major programming-language libraries, servers, Android networking, and Kubernetes tooling. It argues that HTTP/3 rollout beyond browsers and large CDNs remains at an early stage.

## Source excerpt

HTTP/3 has been in development since at least 2016, while QUIC (the protocol beneath it) was first introduced by Google way back in 2013. Both are now standardized, supported in 95% of users' browsers, already used in 32% of HTTP requests to Cloudflare, and support is advertised by 35% of websites (through alt-svc or DNS) in the HTTP Archive dataset. We've developed a totally new version of HTTP, and we're on track to migrate more than 1/3 of web traffic to it already! This is astonishing progress. At the same time, neither QUIC nor HTTP/3 are included in the standard libraries of any major languages including Node.js, Go, Rust, Python or Ruby. Curl recently gained support but it's experimental and disabled in most distributions. There are a rare few external libraries for some languages, but all are experimental and/or independent of other core networking APIs. Despite mobile networking being a key use case for HTTP/3, Android's most popular HTTP library has no support. Popular servers like Nginx have only experimental support, disabled by default, Apache has no support or published plan for support, and Ingress-Nginx (arguably the most popular Kubernetes reverse proxy) has dropped all plans for HTTP/3 support punting everything to a totally new (as yet unreleased) successor project instead. Really it's hard to point to any popular open-source tools that fully support HTTP/3: rollout has barely even started. This seems contradictory. What's going on? I'm going to assume a basic familiarity with the differences between HTTP/1.1 (et al), HTTP/2 and HTTP/3 here. If you're looking for more context, http2-explained and http3-explained from Daniel Stenberg (founder & lead developer of curl) is an excellent guide. Why do we need more than HTTP/1.1? Let's step back briefly. Why does this matter? Who cares about whether HTTP/3 is being rolled out successfully or not? If browser traffic and the big CDNs support HTTP/3, do we even need it in other client or server implementat