This repository contains mod_h[ttp]2 and mod_proxy_h[ttp]2 from Apache httpd as a standalone build. It servers as early access to features and fixes before being shipped in the next Apache release. Both modules can be considered production ready and stable as shipped by the Apache project.

mod_h[ttp]2 is an official Apache httpd module since release 2.4.17. mod_proxy_h[ttp]2 has been added in Apache in 2.4.23. The versions here at github are for more frequent releases than the Apache schedule provides for.

The following beautiful people have directly contributed to this project via commits over the years: Julian Reschke, Lubos Uhliarik, Luca Toscano, MATSUMOTO Ryosuke, Michael Kaufmann, Michael Köller, Mike Frysinger, Nicholas Race, Nicolas Noble, Petri Koistinen, Sam Hurst, Tatsuhiro Tsujikawa.

You need a built Apache httpd 2.4.34 or newer, including apxs and headers to compile and run this module. Additionally, you need an installed libnghttp2, at least in version 1.7.0. And additionally, you want an installed OpenSSL 1.0.2 or later.

tl;dr

You need an installed recent Apache 2.4.x

• Ubuntu: ppa by ondrej for Ubuntu 14.04 and others
• Fedora: shipped in Fedora 23 and later
• Debian sid (unstable) how to install debian sid
• Gentoo: latest stable
• FreeBSD: Apache 2.4 port includes mod_http2 / mod_http2 port

See ChangeLog for details.

I decided to make the test suite part of this repository again. The existing suite resides in test Apache httpd test repository and is a set of shell scripts. It works, but I miss features that professional test frameworks bring. The tests included here use python3 and pytest which I think is an excellent way to do tests. I use it also in my Let's Encrypt module mod_md.

You can build the module without having the test prerequisites. If you want to run them, however, you need pytest, python3 and a curl with http2 support. Then you can

> make
> make test

This module is part of the Apache httpd proxy architecture and functions similar to mod_proxy_http and friends. To configure it, you need to use h2: or h2c: in the proxy URL. Example:

<Proxy "balancer:https://h2-local">
    BalancerMember "h2:https://test.example.org:SUBST_PORT_HTTPS_SUBST"
</Proxy>
<Proxy "balancer:https://h2c-local">
    BalancerMember "h2c:https://test.example.org:SUBST_PORT_HTTP_SUBST"
</Proxy>

<IfModule proxy_http2_module>
    ProxyPass "/h2proxy" "balancer:https://h2-local"
    ProxyPassReverse "/h2proxy" "balancer:https://h2-local"
    ProxyPass "/h2cproxy" "balancer:https://h2c-local"
    ProxyPassReverse "/h2cproxy" "balancer:https://h2c-local"
</IfModule>

This will only work under the following conditions:

• the backend speaks HTTP/2, the module will not fallback to HTTP/1.1
• the backend supports HTTP/2 direct mode (see also H2Direct directive of mod_http2)

All other common httpd proxy directives also apply.

The official Apache documentation of the module.

I also compiled a how to h2 in apache document with advice on how to deploy, configure and verify your mod_h[ttp]2 installation.

Still not dissuaded? Ok, here are some hints to get you started. Building from git is easy, but please be sure that at least autoconf 2.68 is used:

> autoreconf -i
> automake
> autoconf
> ./configure --with-apxs=<path to apxs>
> make

Please see the file called LICENSE.

This work has been funded by the GSM Association (https://gsma.com). The module itself was heavily influenced by mod_spdy, the Google implementation of their SPDY protocol. And without Tatsuhiro Tsujikawa excellent nghttp2 work, this would not have been possible.

Münster, 04.11.2019,

Stefan Eissing, greenbytes GmbH

Copying and distribution of this file, with or without modification, are permitted in any medium without royalty provided the copyright notice and this notice are preserved. This file is offered as-is, without warranty of any kind. See LICENSE for details.