HTTP/2

02/08/2017

2 minutes to read

Contributors

In this article

HTTP/2, the first significant rework of the Hypertext Transfer Protocol since 1999, improves web performance, enabling a more efficient use of network resources and reducing the perception of latency. HTTP/2 introduces header compression (eliminating entire roundtrips of unnecessary network latency), Server Push (an unsolicited push of representations from servers to clients), utilizes multiplexing (allowing multiple concurrent exchanges on the same connection), enables prioritizing while making multiple HTTP requests to a domain, and uses binary protocol (whereas HTTP/1.1 uses text protocol). HTTP/2 does not require any changes to the way that existing web applications work, but adds new features that new applications can take advantage of for increased speed.

Note

Microsoft Edge implements the HTTP/2 standard and has removed support for the experimental SPDY/3 protocol. SPDY/3, also known as TCP Connection Sharing, was an experimental precursor to HTTP/2 that implemented some network use optimizations.

Can I use HTTP/2 now?

HTTP/2 will be used by Microsoft Edge on SSL/TLS connections (https) when supported by the host server. Microsoft Edge will fall back to HTTP/1.1 when HTTP/2 is not available or the connection is not secure. Client-side developers will see HTTP/2 noted in the F12 developer tools Network tool where applicable. To see a list of over thirty independent implementations of the HTTP/2 protocol by clients, servers, intermediaries, and network tools, visit the HTTP/2 Implementations Wiki on GitHub.

What does HTTP/2 do to improve security?

HTTP/2 defines a profile of TLS that is required; this includes the version, a ciphersuite blacklist, and extensions used. See the spec for details.