Most popular distributions still do not offer packages for H2O [1], but it is not difficult to build the web server. In addition to the standard compilation tools, you also need cmake. The following command will help you pick up the code from GitHub:

git clone https://github.com/h2o/h2o.git h2o

Now change to the h2o directory. As the build parameters, you can decide whether to trust OpenSSL for encrypted connections or to go with LibreSSL  [2] instead. To use OpenSSL, type:

cmake -DWITH_BUNDLED_SSL=off

If you prefer the OpenSSL fork, LibreSSL, you can replace off with on. If you stipulate auto, Cmake will check which OpenSSL version exists on your system. If it is newer than 1.0.2, OpenSSL is used, otherwise LibreSSL. The H2O developers prefer LibreSSL because it is generally regarded as more secure and supports procedures such as Chacha20-Poly1305. That said, H2O is a little slower than OpenSSL.

This fact can be significant because H2O owes its burgeoning popularity to its speed. Even before H2O reached version 1.0, benchmarks [3] demonstrating that the newcomer delivered web pages twice as fast as the Nginx sprinter were already making the rounds. H2O also shares the ability to act as a reverse proxy with Nginx.

Bring On the Water!

All that is separating you and a working web server now is two commands: make and sudo make install. The executable is created in /usr/local/bin/, and a sample configuration file exists in the examples directory. I launched the server as follows:

/usr/local/bin/h2o -c \
  /usr/local/h2o/examples/h2o/h2o.conf

In the out-of-the-box configuration, the server listens on port 8080 (unencrypted) and 8081 (with HTTPS). If you have a suitable browser (e.g., Firefox as of version 36), you can even try out the new HTTP/2 protocol, about which another article in this issue reveals many interesting facts.

The browser then complains about the protocol being self-signed, but the setup still works (Figure 1). The new HTTP protocol, which only became an official IETF standard in May 2015, is something that many other web servers still cannot handle. HTTP/2 can bundle connections and also has a new compression method in the form of HPACK.

Figure 1: A new version of Firefox reveals that H2O speaks HTTP/2.