Damn … Apache does, but, Wordpress doesn’t … unless we’ve missed something, but you have to make a choice with Wordpress … either its a https:// site, or its a http:// site … they hard code the protocol / url right into the database …
Any ETA on ALPN on the backend? 1.7? Or not until 1.8? is there a way of setting it up so that haproxy listens HTTP/2 and talks HTTP/1.1 to the backend … ? > On Dec 16, 2015, at 15:34, Lukas Tribus <[email protected]> wrote: > > Hi Marc, > > > >> server web2 119.81.152.73:443 weight 1 maxconn 30 check ssl verify none > > Apache expects that the TLS client negotiates h2 via ALPN, but the TLS client > in > this case is haproxy, so this won't work. > > You have to disable TLS on the backend und go unencrypted. nginx and jetty > can do clear-text http2, I'm not sure about apache. > > > HAproxy doesn't support SNI, NPN or ALPN on the backend currently. > > > > Regards, > > Lukas > >
