67e19ebccd
This patch implements extra variables/keys that can be used to enable HTTP/2 protocol for frontends and backends. With that patch does not add HTTP/2 support for any redirect frontends since they can not be configured to use TLS and this it will cause such redirect backends to be HTTP/2 only, which might break old clients. With that regular frontends, that are not terminating TLS can be configured to be HTTP/2 only as well as TCP backends. Change-Id: Ib14f031f3c61f31bf7aaf345a3ba635ca5fb9ff8
23 lines
788 B
YAML
23 lines
788 B
YAML
---
|
|
features:
|
|
- |
|
|
Added new keys ``haproxy_frontend_h2`` and ``haproxy_backend_h2``
|
|
per service definition to enable HTTP/2 for a specified service.
|
|
|
|
This also add new variables to control default behavoir for
|
|
frontends and backends:
|
|
|
|
* ``haproxy_frontend_h2: true``
|
|
* ``haproxy_backend_h2: false``
|
|
|
|
Please mention, that double stack of HTTP/1.1 and HTTP/2 is only available
|
|
for TLS protected frontends. In case frontend is just TCP
|
|
haproxy_frontend_h2 will be ignored.
|
|
|
|
At the same time ``haproxy_backend_h2`` will be respected regardless of
|
|
TLS/plain TCP configuration.
|
|
upgrade:
|
|
- |
|
|
HTTP/2 is enabled by default for frontends that are covered with TLS.
|
|
You can disable this behaviour by setting ``haproxy_frontend_h2: false``
|