252412316e
This option had always been broken in HTX, which means that the first breakage appeared in 1.9, that it was broken by default in 2.0 and that no workaround existed starting with 2.1. The way this option works is praticularly unfit to the rest of the configuration and to the internal architecture. It had some uses when it was introduced 14 years ago but nowadays it's possible to do much better and more reliable using a set of "http-request set-dst" and "http-request set-uri" rules, which additionally are compatible with DNS resolution (via do-resolve) and are not exclusive to normal load balancing. The "option-http_proxy" example config file was updated to reflect this. The option is still parsed so that an error message gives hints about what to look for. |
||
|---|---|---|
| .. | ||
| errorfiles | ||
| acl-content-sw.cfg | ||
| basic-config-edge.cfg | ||
| content-sw-sample.cfg | ||
| haproxy.init | ||
| option-http_proxy.cfg | ||
| quick-test.cfg | ||
| socks4.cfg | ||
| transparent_proxy.cfg | ||
| wurfl-example.cfg | ||