Jump to content

HTTP/3

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by 108.171.128.173 (talk) at 09:59, 18 October 2019. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

HTTP/3
Developed byIETF
Introduced26 September 2019 (2019-09-26)
Websitehttps://httpwg.org/specs/rfc9114.html

HTTP/3 or H3[1] is the third major version of the Hypertext Transfer Protocol used to exchange binary information on the World Wide Web, succeeding HTTP/2.[2][3] HTTP/3 is a draft based on a previous RFC draft, then named "Hypertext Transfer Protocol (HTTP) over QUIC".[4] QUIC is a transport layer network protocol initially developed by Google where user space congestion control is used over User Datagram Protocol (UDP).

On 28 October 2018 in a mailing list discussion, Mark Nottingham, Chair of the IETF HTTP and QUIC Working Groups, made the official request to rename HTTP-over-QUIC as HTTP/3 to "clearly identify it as another binding of HTTP semantics to the wire protocol ... so people understand its separation from QUIC" and pass its development from the QUIC Working Group to the HTTP Working Group after finalizing and publishing the draft.[5] In the subsequent discussions that followed and stretched over several days, Nottingham's proposal was accepted by fellow IETF members, who in November 2018 gave their official seal of approval that HTTP-over-QUIC become HTTP/3.[4]

Support for HTTP/3 was added to Cloudflare and Chrome (Canary build) in September 2019. Support in Firefox Nightly will be coming later in quarter 3 of 2019.[6]

Software for HTTP/3

Open source libraries to implement both client and server logic for QUIC and HTTP/3 are available, implementing e.g. Google's versions of QUIC (e.g. Q046 used in Chrome 76), and h3-22 the experimental precursor to HTTP/3.[7] Also available is a fast HPACK Huffman Decoder for HTTP/2, also used for "QPACK library, speeding up our HTTP/3 stack".[8] Some of the first adopters of this technology were hosting platform Cloudflare and web browsers Google Chrome and Mozilla Firefox.[9] The popular command-line tool cURL provides a working implementation, also available through the provided library libcurl.[10][11]

See also

References

  1. ^ "Litespeed and Facebook Complete First HTTP/3 Server Test". LiteSpeed Blog. 12 November 2018. Retrieved 2 August 2019.
  2. ^ Bishop, M. (19 September 2019). "Hypertext Transfer Protocol Version 3 (HTTP/3)". quicwg.org. Retrieved 22 September 2019.
  3. ^ Bishop, Mike (12 September 2019). Hypertext Transfer Protocol Version 3 (HTTP/3). IETF. I-D draft-ietf-quic-http-23.
  4. ^ a b Cimpanu, Catalin (12 November 2018). "HTTP-over-QUIC to be renamed HTTP/3 | ZDNet". ZDNet. Retrieved 12 November 2018.
  5. ^ Nottingham, Mark (28 October 2018). "Identifying our deliverables". IETF Mail Archive.
  6. ^ Cimpanu, Catalin (26 September 2019). "Cloudflare, Google Chrome, and Firefox add HTTP/3 support". ZDNet. Retrieved 27 September 2019.
  7. ^ "LiteSpeed's QUIC and HTTP/3 Library is Open Source ⋆ LiteSpeed Blog". LiteSpeed Blog. 11 September 2019. Retrieved 22 September 2019.
  8. ^ "LiteSpeed's Fast Huffman Decoder ⋆ LiteSpeed Blog". LiteSpeed Blog. 16 September 2019. Retrieved 22 September 2019.
  9. ^ Cimpanu, Catalin (26 September 2019). "Cloudflare, Google Chrome, and Firefox Add HTTP/3 Support". ZDNet. Retrieved 26 September 2019.
  10. ^ "First HTTP/3 with curl". Daniel Stenberg. 5 August 2019. Retrieved 2 October 2019.
  11. ^ "cURL HTTP3 wiki". Daniel Stenberg. 26 September 2019. Retrieved 2 October 2019.
Retrieved from "https://en.wikipedia.org/enwiki/w/index.php?title=HTTP/3&oldid=921853077"