Hi Christian,
On Wed, Apr 24, 2019 at 02:29:40PM +0200, Christian Ruppert wrote:
> Hi,
>
> so I did some more tests and it seems to be an issue between h2test_tcp.tls
> and the frontend, using the UNIX sockets. Adding a TCP bind to that listener
> also doesn't work. Am I doing it wrong or is it a bug somewhere with H/2 and
> UNIX sockets?
> I also disabled the PROXY protocol - doesn't help.
I currently have no idea about this one. There should be no reason for
H2 to depend on the underlying socket type.
Hmm wait a minute. It might not be related to the UNIX sockets at all.
In fact what's happening is that your first proxy is not advertising
H2 in the ALPN connection, so the second one doesn't receive it and
negociates H1. You could try to add "alpn h2" at the end of your server
line below :
> listen h2test_tcp
> mode tcp
> bind :444
> option tcplog
> log global
> server socket-444-h2test unix@/run/haproxy-444-h2test.sock send-proxy-v2
^^^^^^^^^
> listen h2test_tcp.tls
> mode tcp
> option tcplog
> log global
> bind unix@/run/haproxy-444-h2test.sock accept-proxy user haproxy
> group haproxy mode 600 ssl crt /etc/haproxy/ssl/h2test.pem alpn h2,http/1.1
> server socket-444_2 unix@/run/haproxy-444_2-h2test.sock send-proxy-v2
^^^^^^^^^
And on this one as well. However it will break your H1. What are you
trying to do exactly ? Maybe there is a simpler solution.
Willy
