9d14f2c764
For historical reasons, the config parser relies on the trailing '\0' to detect the end of the line being parsed. When the lines started to be tokenized into arguments, this principle has been preserved, and now all the parsers rely on *args[arg]='\0' to detect the end of a line. But as reported in issue #2944, while most of the time it breaks the parsing like below: http-request deny if { path_dir '' } it can also cause some elements to be silently ignored like below: acl bad_path path_sub '%2E' '' '%2F' This may also subtly happen with environment variables that don't exist or which are empty: acl bad_path path_sub '%2E' "$BAD_PATTERN" '%2F' Fortunately, parse_line() returns the number of arguments found, so it's easy from the callers to verify if any was empty. The goal of this commit is not to perform sensitive changes, it's only to mention when parsing a line that an empty argument was found and alert about its consequences using a warning. Most of the time when this happens, the config does not parse. But for examples as the ACLs above, there could be consequences that are better detected early. This patch depends on this previous fix: BUG/MINOR: tools: do not create an empty arg from trailing spaces Co-authored-by: Valentine Krasnobaeva <vkrasnobaeva@haproxy.com> |
||
|---|---|---|
| .github | ||
| addons | ||
| admin | ||
| dev | ||
| doc | ||
| examples | ||
| include | ||
| reg-tests | ||
| scripts | ||
| src | ||
| tests | ||
| .cirrus.yml | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .travis.yml | ||
| BRANCHES | ||
| BSDmakefile | ||
| CHANGELOG | ||
| CONTRIBUTING | ||
| INSTALL | ||
| LICENSE | ||
| MAINTAINERS | ||
| Makefile | ||
| README.md | ||
| SUBVERS | ||
| VERDATE | ||
| VERSION | ||
HAProxy
HAProxy is a free, very fast and reliable reverse-proxy offering high availability, load balancing, and proxying for TCP and HTTP-based applications.
Installation
The INSTALL file describes how to build HAProxy. A list of packages is also available on the wiki.
Getting help
The discourse and the mailing-list are available for questions or configuration assistance. You can also use the slack or IRC channel. Please don't use the issue tracker for these.
The issue tracker is only for bug reports or feature requests.
Documentation
The HAProxy documentation has been split into a number of different files for ease of use. It is available in text format as well as HTML. The wiki is also meant to replace the old architecture guide.
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)
License
HAProxy is licensed under GPL 2 or any later version, the headers under LGPL 2.1. See the LICENSE file for a more detailed explanation.