Quantcast
Channel: HAProxy community - Latest topics
Viewing all articles
Browse latest Browse all 4735

400 Bad request when enabling HTTP/2

$
0
0

Hi all,
Basically I want to enable http/2 protocol on my HAproxy. I successfully upgraded from v1.7.5 to v1.8.28 and as per examples added alpn h2,http/1.1 to my bind where ssl crt already was like so

bind 2.2.2.2:443 ssl crt cert.pem alpn h2,http/1.1

After reloading config and trying to access my page, it shows 400 Bad request error from HAproxy and in logs it shows this with CH flag
frontend~ backend/backend-server 0/0/1/-1/2 400 188 - - CH-- 2/2/0/0/0 0/0 "GET / HTTP/1.1"

Everything works fine if I dont add alpn h2,http/1.1 to config.
Also I noticed that if I bypass nginx on my backend, it also works. For example I am running Rancher behind HAproxy for my apps and if I set backend to not use Rancher nginx ingress, but connect straight to dedicated port, it works.
Also it works bypassing HAproxy itself, setting Rancher nginx ingress in hosts file and accessing my app, in chrome dev tools I see that it loads using h2 protocol just fine.

Any idea what might cause the 400 bad request?
Regards

1 post - 1 participant

Read full topic


Viewing all articles
Browse latest Browse all 4735

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>