mirror of
https://github.com/haproxy/haproxy.git
synced 2026-02-19 02:29:31 -05:00
41d906d69b
There are some variables, which are set by HAProxy process (HAPROXY_*). Some of them are handy to check or to redefine in the configuration, in order to create conditional blocks and make the configuration more flexible. But it wasn't clear in the documentation, which variables are really safe and usefull to redefine and which ones could be only read via "show env" output. Latest changes in master-worker architecture makes the existed description even more confusing. So let's sort all HAPROXY_* variables to four categories and let's also mark explicitly, which ones are set in which process, when haproxy is started in master-worker mode. In addition, update examples in chapter "2.4. Conditional blocks". This might bring more ideas for users how HAPROXY_* variables could be used in the conditional blocks. |
||
|---|---|---|
| .. | ||
| design-thoughts | ||
| internals | ||
| lua-api | ||
| 51Degrees-device-detection.txt | ||
| acl.fig | ||
| coding-style.txt | ||
| configuration.txt | ||
| cookie-options.txt | ||
| DeviceAtlas-device-detection.txt | ||
| gpl.txt | ||
| haproxy.1 | ||
| HAProxyCommunityEdition_60px.png | ||
| intro.txt | ||
| lgpl.txt | ||
| linux-syn-cookies.txt | ||
| lua.txt | ||
| management.txt | ||
| netscaler-client-ip-insertion-protocol.txt | ||
| network-namespaces.txt | ||
| peers-v2.0.txt | ||
| peers.txt | ||
| proxy-protocol.txt | ||
| queuing.fig | ||
| regression-testing.txt | ||
| seamless_reload.txt | ||
| SOCKS4.protocol.txt | ||
| SPOE.txt | ||
| WURFL-device-detection.txt | ||
