You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 4, 2024. It is now read-only.
the Haproxy supports h2 frontend support and I tried to enable it with marathon-lb. I took a while but finally I was successful.
I created the following overwrite template HAPROXY_HTTPS_FRONTEND_HEAD file (including the leading and post empty line) and added into the template folder.
If you keep the defaults ssl_fc_sni based routing and multi domains or wildcard certificates, you will face the http2 reuse problem, all frontends using the same ssl certificate will be mixed.
Hi,
the Haproxy supports h2 frontend support and I tried to enable it with marathon-lb. I took a while but finally I was successful.
I created the following overwrite template HAPROXY_HTTPS_FRONTEND_HEAD file (including the leading and post empty line) and added into the template folder.
``
frontend marathon_https_in
bind *:443 ssl {sslCerts} alpn h2,http/1.1
mode http
``
Can you document it as example or add a config parameter to be able to configure alpn protocols?
The text was updated successfully, but these errors were encountered: