mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-09-22 06:11:32 +02:00
12882cfaf8
First, when a server health check is initialized, it inherits the mux protocol from the server if it is not already specified. Because there is no option to specify the mux protocol for the checks, it is always inherited from the server for now. Then, if the connect rule is configured to use the server options, the mux protocol of the check is used, if defined. Of course, if a mux protocol is already defined for the connect rule, it is used in priority. But for now, it is not possible. Thus, if a server is configured to use, for instance, the h2 protocol, it is possible to do the same for the health-checks. No backport needed.
The HAProxy documentation has been split into a number of different files for ease of use. Please refer to the following files depending on what you're looking for : - INSTALL for instructions on how to build and install HAProxy - BRANCHES to understand the project's life cycle and what version to use - LICENSE for the project's license - CONTRIBUTING for the process to follow to submit contributions The more detailed documentation is located into the doc/ directory : - doc/intro.txt for a quick introduction on HAProxy - doc/configuration.txt for the configuration's reference manual - doc/lua.txt for the Lua's reference manual - doc/SPOE.txt for how to use the SPOE engine - doc/network-namespaces.txt for how to use network namespaces under Linux - doc/management.txt for the management guide - doc/regression-testing.txt for how to use the regression testing suite - doc/peers.txt for the peers protocol reference - doc/coding-style.txt for how to adopt HAProxy's coding style - doc/internals for developer-specific documentation (not all up to date)