mirror of
https://github.com/haproxy/haproxy.git
synced 2026-02-03 20:39:41 -05:00
6ea50ba462
From time to time, issues are reported about string matching based on suffix (for instance path_beg). Each time, it appears these ACLs are used in conjunction with a converter or followed by an explicit matching method (-m). Unfortunatly, it is not an issue but an expected behavior, while it is not obvious. matching suffixes can be consider as aliases on the corresponding '-m' matching method. Thus "path_beg" is equivalent to "path -m beg". When a converter is used the original matching (string) is used and the suffix is lost. When followed by an explicit matching method, it overwrites the matching method based on the suffix. It is expected but confusing. Thus now a warning is emitted because it is a configuration issue for sure. Following sample fetch functions are concerned: * base * path * req.cook * req.hdr * res.hdr * url * urlp The configuration manual was modified to make it less ambiguous. |
||
|---|---|---|
| .. | ||
| 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 | ||
