mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2026-01-19 00:51:37 +01:00
57e4a1bf44
Always set frontend HTTP analysers when an HTX stream is created. It is only useful in case a destructive HTTP upgrades (TCP>H2) because the frontend is a TCP proxy. In fact, to be strict, we must only set these analysers when the upgrade is performed before setting the backend (it is not supported yet, but this patch is required to do so), in the frontend part. If the upgrade happens when the backend is set, it means the HTTP processing is just the backend buisness. But there is no way to make the difference when a stream is created, at least for now.
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)