mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-08-10 00:57:02 +02:00
13403761d5
Some custom actions are just ignored and skipped when an error is encoutered. In that case, we jump to the next rule. To do so, most of them use the return code ACT_RET_ERR. Currently, for http rules and tcp content rules, it is not a problem because this code is handled the same way than ACT_RET_CONT. But, it means there is no way to handle the error as other actions. The custom actions must handle the error and return ACT_RET_DONE. For instance, when http-request rules are processed, an error when we try to replace a header value leads to a bad request and an error 400 is returned to the client. But when we fail to replace the URI, the error is silently ignored. This difference between the custom actions and the others is an obstacle to write new custom actions. So, in this first patch, ACT_RET_CONT is now returned from custom actions instead of ACT_RET_ERR when an error is encoutered if it should be ignored. The behavior remains the same but it is now possible to handle true errors using the return code ACT_RET_ERR. Some actions will probably be reviewed to determine if an error is fatal or not. Other patches will be pushed to trigger an error when a custom action returns the ACT_RET_ERR code. This patch is not tagged as a bug because it is just a design issue. But others will depends on it. So be careful during backports, if so. |
||
|---|---|---|
| .github/ISSUE_TEMPLATE | ||
| contrib | ||
| doc | ||
| ebtree | ||
| examples | ||
| include | ||
| reg-tests | ||
| scripts | ||
| src | ||
| tests | ||
| .cirrus.yml | ||
| .gitignore | ||
| .travis.yml | ||
| BRANCHES | ||
| CHANGELOG | ||
| CONTRIBUTING | ||
| INSTALL | ||
| LICENSE | ||
| MAINTAINERS | ||
| Makefile | ||
| README | ||
| ROADMAP | ||
| 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)