After a 15-year wait since HTTP/1.1 the next major version of HTTP was finally published.
HTTP/2 (originally named HTTP/2.0) is the second major version of the HTTP network protocol used by the World Wide Web. It is based on SPDY. HTTP/2 was developed by the Hypertext Transfer Protocol working group (httpbis, where bis means ?second?) of the Internet Engineering Task Force. HTTP/2 is the first new version of HTTP since HTTP 1.1, which was standardized in RFC 2068 in 1997
HTTP/2 maintains heigh-level compatibility with HTTP/1.1 and decreases latency to improve page load speed in web browsers. In addition, most commonly used web server support it friendly and also it’s easy to configure, so it’s a nice choice to upgrade the your site’s protocol from HTTP/1.1 to HTTP/2.
- Apache 2.4.17, the first version of Apache2 with mod_http2 build in(mod_http2 is the renamed mod_h2 module).
So, if you have an Apache2 with a version under minimum requirement installed, you have to upgrade it first. In general, it is easy and friendly to upgrade apache2 to a newer or latest version on most popular OS.
- In short, HTTP/2 protocol does not require SSL, add the following lines in your sites configurations.
Restart or reload your web server to make the configuration active.
There are thousands of methods to test whether your sites are using HTTP/2.
- Check response header in Developer Tools of Google Chrome web browser.
Chrome web browser supports a powerful tools for web developer, you can check network response header in “Network” tab, and if your site are compatible with HTTP/2, you can find HTTP/2 after http version label.
- Request for header with cURL
cURL can only request head with -I option to reduce verbose information. In the graph below, HTTP/2 version is clearly showed in the second line in the output.