International standardBishop, Mike; Akamai. "RFC 9114: HTTP/3". rfc-editor. Retrieved 6 June 2022. (HTTP/3 also uses the completed QUIC protocol described in RFC 9000 and related RFCs such as RFC 9001)
Developed byIETF
IntroducedRFC 9114

HTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web, complementing the widely-deployed HTTP/1.1 and HTTP/2. Unlike previous versions which relied on the well-established TCP (published in 1974), HTTP/3 uses QUIC, a multiplexed transport protocol built on UDP. On 6 June 2022, IETF published HTTP/3 as a Proposed Standard in RFC 9114.

HTTP/1Transport Layer SecurityTransmission Control ProtocolHTTP/2TLS 1.2Transmission Control ProtocolHTTP/3TLS 1.3QUICUser Datagram ProtocolInternet Protocol
About this image
Protocol Stack of HTTP/3 compared to HTTP/1.1 and HTTP/2

HTTP/3 uses similar semantics compared to earlier revisions of the protocol, including the same request methods, status codes, and message fields, but encodes them and maintains session state differently. However, partially due to the protocol's adoption of QUIC, HTTP/3 has lower latency and loads more quickly in real-world usage when compared with previous versions: in some cases over 3× faster than with HTTP/1.1 (which remains the only HTTP version deployed by many websites).

HTTP/3 is supported by 75% of web browsers (and 83% of "tracked desktop" web browsers), and 26% of the top 10 million websites. It has been supported by Chromium (and derived projects including Google Chrome, Microsoft Edge, Samsung Internet, and Opera) since April 2020 and by Mozilla Firefox since May 2021. Safari 14 (on macOS Big Sur and iOS 14, and "is a major new feature in iOS 15"; for apps) implemented the protocol but it remains disabled by default.


HTTP/3 originates from an Internet Draft adopted by the QUIC working group. The original proposal was named "HTTP/2 Semantics Using The QUIC Transport Protocol", and later renamed "Hypertext Transfer Protocol (HTTP) over QUIC".

On 28 October 2018 in a mailing list discussion, Mark Nottingham, Chair of the IETF HTTP and QUIC Working Groups, proposed renaming HTTP-over-QUIC to HTTP/3, to "clearly identify it as another binding of HTTP semantics to the wire protocol [...] so people understand its separation from QUIC". Nottingham's proposal was accepted by fellow IETF members a few days later. The HTTP working group was chartered to assist the QUIC working group during the design of HTTP/3, then assume responsibility for maintenance after publication.

Support for HTTP/3 was added to Chrome (Canary build) in September 2019 and then eventually reached stable builds, but was disabled by a feature flag. It was enabled by default in April 2020. Firefox added support for HTTP/3 in November 2019 through a feature flag and started enabling it by default in April 2021 in Firefox 88. Experimental support for HTTP/3 was added to Safari Technology Preview on April 8, 2020 and was included with Safari 14 that ships with iOS 14 and macOS 11, but it's still disabled by default as of Safari 16, on both macOS and iOS.[citation needed]

Comparison with HTTP/1.1 and HTTP/2

HTTP semantics are consistent across versions: the same request methods, status codes, and message fields are typically applicable to all versions. The differences are in the mapping of these semantics to underlying transports. Both HTTP/1.1 and HTTP/2 use TCP as their transport. HTTP/3 uses QUIC, a transport layer network protocol which uses user space congestion control over the User Datagram Protocol (UDP). The switch to QUIC aims to fix a major problem of HTTP/2 called "head-of-line blocking": because the parallel nature of HTTP/2's multiplexing is not visible to TCP's loss recovery mechanisms, a lost or reordered packet causes all active transactions to experience a stall regardless of whether that transaction was impacted by the lost packet. Because QUIC provides native multiplexing, lost packets only impact the streams where data has been lost.

Proposed DNS resource records SVCB (service binding) and HTTPS would allow connecting without first receiving the Alt-Svc header via previous HTTP versions, therefore removing the 1 RTT of handshaking of TCP. There is client support for HTTPS resource records since Firefox 92, iOS 14, reported Safari 14 support, and Chromium supports it behind a flag.




Browser support for HTTP/3
Browser Version implemented (disabled by default) Version shipped (enabled by default) Comment
Chrome Stable build (79) December 2019 87 April 2020 Earlier versions implemented other drafts of QUIC
Edge Stable build (79) December 2019 87 April 2020 Edge 79 was the first version based on Chromium
Firefox Stable build (72.0.1) January 2020 88 April 2021
Safari Safari Technology Preview 104 April 2020  –  –


Open-source libraries that implement client or server logic for QUIC and HTTP/3 include

Libraries implementing HTTP/3
Name Client Server Programming language Company Repository
lsquic Yes Yes C LiteSpeed
nghttp3 Yes Yes C
h2o No Yes C
libcurl Yes No C
MsQuic Yes Yes C Microsoft
proxygen Yes Yes C++ Facebook
Cronet Yes Yes C++ Google
.NET Yes Yes C# (using MsQuic) Microsoft
quic-go Yes Yes Go
http3 Yes Yes Haskell
Kwik Yes Yes Java
Flupke Yes Yes Java
aioquic Yes Yes Python
quiche Yes Yes Rust Cloudflare
neqo Yes Yes Rust Mozilla
quinn Yes Yes Rust
s2n-quic Yes Yes Rust Amazon Web Services


  • On 7 June 2021, LiteSpeed Web Server (and OpenLiteSpeed) 6.0.2 was released and became the first version to enable HTTP/3 by default.
  • Caddy web server v2.6.0 (released 20 September 2022) has HTTP/3 enabled by default.
  • Nginx support for HTTP/3 is being worked on. A technology preview of nginx with HTTP/3 support was released in June 2020.
  • Cloudflare distributes a patch for nginx that integrates the quiche HTTP/3 library into it.
  • Microsoft IIS support for HTTP/3 is enabled natively with Windows Server 2022/Windows 11.
  • HAProxy supports HTTP/3 over QUIC since version 2.6 released on 31 May 2022.

See also

This page was last updated at 2023-02-23 12:06 UTC. Update now. View original page.

All our content comes from Wikipedia and under the Creative Commons Attribution-ShareAlike License.


If mathematical, chemical, physical and other formulas are not displayed correctly on this page, please useFirefox or Safari