HTTP/2

HTTP/2
International standardRFC 9113
Developed byIETF
IntroducedMay 14, 2015; 9 years ago (2015-05-14)
Websitehttps://http2.github.io/

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.[1][2] HTTP/2 was developed by the HTTP Working Group (also called httpbis, where "bis" means "twice") of the Internet Engineering Task Force (IETF).[3][4][5] HTTP/2 is the first new version of HTTP since HTTP/1.1, which was standardized in RFC 2068 in 1997. The Working Group presented HTTP/2 to the Internet Engineering Steering Group (IESG) for consideration as a Proposed Standard in December 2014,[6][7] 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).[8][9] The initial HTTP/2 specification was published as RFC 7540 on May 14, 2015.[10]

The standardization effort was supported by Chrome, Opera, Firefox,[11] Internet Explorer 11, Safari, Amazon Silk, and Edge browsers.[12] Most major browsers had added HTTP/2 support by the end of 2015.[13] About 97% of web browsers used have the capability (and 100% of "tracked desktop" web browsers).[13] As of July 2023, 36% (after topping out at just over 50%) of the top 10 million websites support HTTP/2.[14]

Its successor is HTTP/3, a major revision that builds on the concepts established by HTTP/2.[2][15][13][16]

  1. ^ Bright, Peter (February 18, 2015). "HTTP/2 finished, coming to browsers within weeks". Ars Technica. Archived from the original on March 30, 2019.
  2. ^ a b Cimpanu, Catalin (November 12, 2018). "HTTP-over-QUIC to be renamed HTTP/3". ZDNet. Retrieved November 19, 2018.
  3. ^ Thomson, M.; Belshe, M.; Peon, R. (November 29, 2014). "Hypertext Transfer Protocol version 2: draft-ietf-httpbis-http2-16". Ietf Datatracker. HTTPbis Working Group. Retrieved February 11, 2015.
  4. ^ Cite error: The named reference charter was invoked but never defined (see the help page).
  5. ^ "IETF HTTP Working Group". httpwg.org. Retrieved December 15, 2019.
  6. ^ "History for draft-ietf-httpbis-http2-16". IETF. Retrieved January 3, 2015. 2014-12-16 IESG state changed to Publication Requested
  7. ^ Raymor, Brian (August 6, 2014). "Wait for it – HTTP/2 begins Working Group Last Call!". Microsoft Open Technologies. Archived from the original on October 6, 2014. Retrieved October 17, 2018.
  8. ^ The IESG (February 17, 2015). "Protocol Action: 'Hypertext Transfer Protocol version 2' to Proposed Standard (draft-ietf-httpbis-http2-17.txt)". httpbis (Mailing list). Retrieved February 18, 2015.
  9. ^ Mark Nottingham (February 18, 2015). "HTTP/2 Approved". ietf.org. Internet Engineering Task Force. Retrieved March 8, 2015.
  10. ^ Belshe, M.; Peon, R.; Thomson, M. (May 2015). Thomson, M (ed.). "RFC 7540 - Hypertext Transfer Protocol Version 2 (HTTP/2)". IETF. doi:10.17487/RFC7540. Retrieved May 14, 2015. {{cite journal}}: Cite journal requires |journal= (help)
  11. ^ "See what's new in Firefox!". www.mozilla.org. Mozilla Foundation. February 2015.
  12. ^ "Can the rise of SPDY threaten HTTP?". blog.restlet.com. Restlet, Inc. October 2011. Archived from the original on January 6, 2014. Retrieved July 23, 2012.
  13. ^ a b c ""HTTP/2" | Can I use... Support tables for HTML5, CSS3, etc". canIuse.com. Retrieved April 3, 2023.
  14. ^ "Usage of HTTP/2 for websites". World Wide Web Technology Surveys. W3Techs. Retrieved July 10, 2023.
  15. ^ Bishop, Mike (July 9, 2019). "Hypertext Transfer Protocol Version 3 (HTTP/3)". Ietf Datatracker. Retrieved July 31, 2019.
  16. ^ Cimpanu, Catalin (26 September 2019). "Cloudflare, Google Chrome, and Firefox add HTTP/3 support". ZDNet. Retrieved 27 September 2019.