HTTP/2
Also known as HTTP 2.0, HTTP/2.0, HTTP 2, H2
HTTP/2 (originally named HTTP/2.0) is a major revision of the HTTP network protocol used by the World Wide Web. It was derived from the earlier experimental SPDY protocol, originally developed by Google. HTTP/2 was developed by the HTTP Working Group (also called httpbis, where "" means "twice" in Latin) of the Internet Engineering Task Force (IETF). HTTP/2 is the first new version of HTTP since HTTP/1.1, which was standardized in in 1997. The Working Group presented HTTP/2 to the Internet Engineering Steering Group (IESG) for consideration as a Proposed Standard in December 2014, and IESG app
Key facts
- Protocol.developer
- IETF
- Protocol.newer
- HTTP/3
via Wikipedia infobox
Official website
HTTP/2
http2.github.io →Link to the official site · 1,655 chars · not written by Vinony
Described at
Implementations · httpwg/http2-spec Wiki · GitHub
Working copy of the HTTP/2 Specification. Contribute to httpwg/http2-spec development by creating an account on GitHub.
github.com →You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert This wiki tracks known implementations of HTTP/2. See also our Tools listing . Ace Elixir client, server ALPN h2 Aerys PHP server ALPN, Upgrade, direct h2, h2c Akamai GHost C++ intermediary ALPN, NPN h2, h2-14 Apache HTTP Server 2.4.17+ C server ALPN, Upgrade, direct h2, h2c Apache HttpComponents 5.0-beta1 Java client,server ALPN, Upgrade, direct h2 Apache Traffic Server v5.3.0 C++ intermediary ALPN, NPN h2, h2-14 Apache Tomcat 8.5+ Java Server ALPN, Upgrade, direct h2, h2c Armeria Java client, server ALPN, Upgrade, direct h2, h2c http4s-blaze Scala server ALPN h2, h2-14 Brocade Traffic Manager (formerly Riverbed/Zeus TM) C++ Server ALPN, Upgrade, direct h2, h2c Chatterbox Erlang Server, Client ALPN h2 Chromium C++ client ALPN h2, h2-14 Chicken Scheme hpack lib Chicken Scheme hpack direct h2-14 cl-http2-protocol Common Lisp client, server NPN, direct h2-14 curl and libcurl C client ALPN, NPN, Upgrade, Direct h2-14, h2c-14 Cutelyst C++ 2.0+ Server ALPN, NPN, Upgrade, Direct h2, h2c Dart Dart client, server ALPN, direct h2 Deuterium C client, server ALPN, direct h2, h2-14, h2c, h2c-14 E2 Systems PATH C Client, Proxy, Server (Testing tool) ALPN h2 elixir-hpack Elixir HPACK Ericsson MSP proxy NPN, Upgrade, direct h2, h2-14, h2c, h2c-14 F5 C server, proxy ALPN, NPN h2 (from BIG-IPv12.0.0 onwards) GFE C++ intermediary ALPN, NPN h2 HAProxy C 1.8+ intermediary ALPN, NPN h2 h2 Rust client, server h2, h2c H2O C Server, proxy ALPN, NPN, Upgrade, direct h2, h2-14, h2-16 HH C Server ALPN h2 Haskell http2 lib Haskell HPACK, framing hpack Erlang HPACK hpack Swift HPACK http-2 Ruby server, client ALPN, NPN, Upgrade, direct h2, h2c, h2-17 http2 Go client, server NPN, ALPN h2, h2-14 http2 Go server, client ALPN, Upgrade h2, h2c http2-client Haskell client ALPN, direct h2 http2dotnet C server, client ALPN & NPN (external), Upgrade, direct h2, h2c HttpTwo C client direct h2, h2c httpbis Rust client, server hyper Python client, server NPN, ALPN h2, h2c Shaka Technologies Ishlangu Load Balancer C, Java server, proxy ALPN h2 Jetty Java client, intermediary, server ALPN, Upgrade, Direct h2, h2-17, h2-14, h2c, h2c-17 libcno C / Python wrapper Server, Client, HPACK ALPN, Upgrade, direct h2, h2c LiteSpeed Enterprise C++ Server ALPN, NPN, Upgrade h2, h2-17, h2-14, h2c ls-hpack C HPACK lua-http Lua client, server ALPN, direct h2 Lucid Erlang Server NPN, direct h2, h2-16, h2-14 Microsoft C/C++ Client, Server ALPN h2 Microsoft Internet Explorer client ALPN (others?) h2 (Windows 10 only?) mod h2 C Server ALPN, Upgrade, direct h2, h2c Mozilla Firefox C++ 49 client ALPN, NPN h2-15, h2-14, h2 Netty Java client, server ALPN, NPN, Upgrade, direct h2, h2c Nimble Streamer C++ 3.6.2-1 server ALPN h2 Live HLS and MPEG-DASH only nghttp2 C client, server, intermediary ALPN, NPN, Upgrade, direct h2, h2-16, h2-14, h2c Radware C++/C proxy, server ALPN h2 NGINX C 1.9.5+ server ALPN, NPN, direct h2, h2c Open Source NGINX 1.9.5 Released with HTTP/2 Support Node.js Node.js 8.4.0+ server, client ALPN, NPN, direct h2, h2c node-http2 Node.js server, client ALPN, NPN, direct h2 node-spdy Node.js server, client ALPN, NPN, direct h2, h2c nuster C 1.8+ intermediary ALPN, NPN h2 OkHttp Android, Java mock server, client ALPN, NPN h2 ocaml-h2 OCaml server, client ALPN, Upgrade, direct h2, h2c Fast Android Networking Android, Java client ALPN, NPN h2 OpenLiteSpeed C++ Server ALPN, NPN, Upgrade h2, h2-17 , h2-14, h2c Protocol::HTTP2 Perl server, client ALPN, NPN, Upgrade, direct h2, h2c River Elixir client ALPN h2 Sasazka Node.js server NPN second-transfer Haskell server ALPN h2-14, h2 ShimmerCat Haskell server ALPN, Ahead Of Time Transfer Engine h2 SuaveIO F server h2 (not yet ready, pull req: ) Swoole PHP server ALPN, NPN, direct h2, h2c Trusterd
~15 min read
Article
17 sectionsContents
- Goals
- Differences from HTTP/1.1
- History
- Genesis in and later differences from SPDY
- Development milestones
- Encryption
- Criticisms
- Development process
- Encryption
- TCP head-of-line blocking
- Server-side support
- Server software
- Content delivery networks
- Implementations
- See also
- References
- External links
HTTP/2 (originally named HTTP/2.0) is a major revision of the HTTP network protocol used by the World Wide Web. It was derived from the earlier experimental SPDY protocol, originally developed by Google. HTTP/2 was developed by the HTTP Working Group (also called httpbis, where "" means "twice" in Latin) of the Internet Engineering Task Force (IETF). HTTP/2 is the first new version of HTTP since HTTP/1.1, which was standardized in in 1997. The Working Group presented HTTP/2 to the Internet Engineering Steering Group (IESG) for consideration as a Proposed Standard in December 2014, and IESG approved it to publish as Proposed Standard on February 17, 2015 (and was updated in February 2020 in regard to TLS 1.3 and again in June 2022). The initial HTTP/2 specification was published as RFC 7540 on May 14, 2015.
The standardization effort was supported by the Chrome, Opera, Firefox, Internet Explorer 11, Safari, Amazon Silk, and Edge browsers. Most major browsers had added HTTP/2 support by the end of 2015. About 97% of web browsers used have the capability (and 100% of "tracked desktop" web browsers). , 36% (after topping out at just over 50%) of the top 10 million websites support HTTP/2.