cbebdb4ba8
Existing "compression" filter is a multi-purpose filter that will try to compress both requests and responses according to "compression" settings, such as "compression direction". One of the pre-requisite work identified to implement decompression filter is that we needed a way to manually define the sequence of enabled filters to chain them in the proper order to make compression and decompression chains work as expected in regard to the intended use-case. Due to the current nature of the "compression" filter this was not possible, because the filter has a combined action as it will try to compress both requests and responses, and as we are about to implement "filter-sequence" directive, we will not be able to change the order of execution of the compression filter between requests and responses. A possible solution we identified to solve this issue is to split the existing "compression" filter into 2 distinct filters, one which is request-oriented, "comp-req", and another one which is response-oriented "comp-res". This is what we are doing in this commit. Compression logic in itself is unchanged, "comp-req" will only aim to compress the request while "comp-res" will try to compress the response. Both filters will still be invoked on request and responses hooks, but they only do their part of the job. From now on, to compress both requests and responses, both filters have to be enabled on the proxy. To preserve original behavior, the "compression" filter is still supported, what it does is that it instantiates both "comp-req" and "comp-res" filters implicitly, as the compression filter is now effectively split into 2 separate filters under the hood. When using "comp-res" and "comp-req" filters explicitly, the use of the "compression direction" setting is not relevant anymore. Indeed, the compression direction is assumed as soon as one or both filters are enabled. Thus "compression direction" is kept as a legacy option in order to configure the "compression" generic filter. Documentation was updated.
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.