mirror of
https://github.com/haproxy/haproxy.git
synced 2026-03-28 13:24:28 -04:00
HAProxy - Load balancer
11a707ae52
When a ring section is parsed, a proxy is created. For now, it has the frontend (PR_CAP_FE) and the internal (PR_CAP_INT) capabilities, in addition to the expected backend capability (PR_CAP_BE). PR_CAP_INT capability was added to silent warning triggered because of PR_CAP_FE capability. Indeed, Because the proxy is declared as a frontend, warnings about missing bind lines and missing client timeout should be triggered during the configuration parsing. These warnings are inhibited because PR_CAP_INT capability is set. It is an issue on the 2.4 because PR_CAP_INT capability does not exist. So warnings are always emitted. But the true bug is that these proxies should not have PR_CAP_FE and PR_CAP_INT capabilities. Removing these capabilities is enough to remove any warnings on the 2.4, with no regression on higher versions. However, it may be a good idea to eval if a dedicated frontend for sinks should be added or not. This way, a true frontend would be used to start the sink applets. In addition, proxies capabilities/modes have to be reviewed to have a less ambiguous API. For instance a dedicate mode for sinks (PR_MODE_SINK ?) may be added. Finally, it could be very nice to have all proxies in the same list, including internal ones. This patch should fix the issue #1900. It must be backported as far as 2.4. |
||
|---|---|---|
| .github | ||
| addons | ||
| admin | ||
| dev | ||
| doc | ||
| examples | ||
| include | ||
| reg-tests | ||
| scripts | ||
| src | ||
| tests | ||
| .cirrus.yml | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .travis.yml | ||
| BRANCHES | ||
| CHANGELOG | ||
| CONTRIBUTING | ||
| INSTALL | ||
| LICENSE | ||
| MAINTAINERS | ||
| Makefile | ||
| README | ||
| SUBVERS | ||
| VERDATE | ||
| VERSION | ||
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)