HTTP/2

Почти всички от най-разпространените браузъри го поддържат от краят на 2015 г.

As of July 2023, 36% (after topping out at just over 50%) of the top 10 million websites support HTTP/2.

Its successor is HTTP/3, a major revision that builds on the concepts established by HTTP/2.

  • Притежава т.н. negotiation mechanism, позволяващ използването на по-стария HTTP 1.1. Create a negotiation mechanism that allows clients and servers to elect to use HTTP/1.1, 2.0, or potentially other non-HTTP protocols.
  • Напълно съвместим е с HTTP 1.1 откъм методи (GET, POST…), статус кодове, хедъри… Maintain high-level compatibility with HTTP/1.1 (for example with methodsstatus codesURIs, and most header fields).
  • По-оптимални зареждане на URL ресурсите чрез: header compression, server push (deprecated), TCP connection multiplexing, prioritization of requests.
  • It is fully multiplexed, sending multiple requests in parallel over a single TCP connection.
  • HTTP/2 is binary, instead of textual. This gives the ability for HTTP/2 to be multiplexed, meaning that it can receive multiple requests at a time over just one connection instead of having to have multiple connections to complete requests.

Използването на HTTP/2 при условие, че досега е използван HTTP 1.1, не изисква никакви промени по web приложението.
The proposed changes do not require any changes to how existing web applications work, but new applications can take advantage of new features for increased speed. HTTP/2 leaves all of HTTP/1.1’s high-level semantics, such as methodsstatus codesheader fields, and URIs, the same. What is new is how the data is framed and transported between the client and the server.

Литература:

https://en.wikipedia.org/wiki/HTTP/2

https://dzone.com/articles/understanding-http2

https://tools.keycdn.com/http2-test

https://blog.fiverr.com/post/http2-is-your-site-using-it-heres-how-you-can-check

https://en.wikipedia.org/wiki/HTTP/3