Mod_proxy_http2 - got a 503

Hello all

We are trying to use the mod_proxy_http2 of httpd. Our use case is for now
- multiple backedns (configured in HTTP2)
- one httpd acting as proxy
-- mod_proxy_http2 is activated
-- we use the Balancer directive to load balanced accross backends
- the client is a curl -kv --http2 ...

The tests are the following:
- while using curl to access one of the backend directly, the access log
shows that we use HTTP/2
- then the balancer directive is configured with <a href="http://mybackend1" title="http://mybackend1">http://mybackend1</a>
In taht case, while accessing to the proxy with curl, we see that the
communication between curl & httpd is HTTP/2 but that the communication
with the backends is HTTP1/1
- then we change the balancer directive to h2://mybackend....
In that case, the curl returns 503 (like if the proxy is unable to route).

I suspect a misconfiguration but any help is welcomed. Does someone already
did something similar?



Re: Mod_proxy_http2 - got a 503

By Stefan Eissing at 06/17/2017 - 12:54


do you talk http: or https: to the backend? h2://mybackend is for the SSL case, for unencrypted calls, use h2c://mybackend.

Maybe that is the problem?


Re: Mod_proxy_http2 - got a 503

By Olivier Mallassi at 06/17/2017 - 16:27

thanks for the help but it does not seem to be this.

my proxy config (extract) is minmum
ProxyPass / balancer://mycluster/
ProxyPassReverse / balancer://mycluster/

<Proxy balancer://mycluster>
BalancerMember h2://localhost:8081

note that everything is running on the same machine for now.

In the httpd error_log, I see
[Sat Jun 17 22:26:32.174438 2017] [ssl:info] [pid 77593:tid
140135766828800] [remote] AH01964: Connection to child 0
established (server xxxx:443)
[Sat Jun 17 22:26:32.176707 2017] [http2:warn] [pid 77593:tid
140135766828800] [client] h2_mplx(78): task(78-1) has
not-shutdown engine(ngn-78-1)

On Sat, Jun 17, 2017 at 6:54 PM, Stefan Eissing <

Re: Mod_proxy_http2 - got a 503

By Eric Covener at 06/17/2017 - 17:04

On Sat, Jun 17, 2017 at 4:27 PM, Olivier Mallassi
<olivier. ... at gmail dot com> wrote:
I suggest re-reading Stefan's reply.