mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-09-21 22:01:31 +02:00
ce9e7b2521
The accept-encoding normalizer now explicitely manages a subset of encodings which will all have their own bit in the encoding bitmap stored in the cache entry. This way two requests with the same primary key will be served the same cache entry if they both explicitely accept the stored response's encoding, even if their respective secondary keys are not the same and do not match the stored response's one. The actual hash of the accept-encoding will still be used if the response's encoding is unmanaged. The encoding matching and the encoding weight parsing are done for every subpart of the accept-encoding values, and a bitmap of accepted encodings is built for every request. It is then tested upon any stored response that has the same primary key until one with an accepted encoding is found. The specific "identity" and "*" accept-encoding values are managed too. When storing a response in the key, we also parse the content-encoding header in order to only set the response's corresponding encoding's bit in its cache_entry encoding bitmap. This patch fixes GitHub issue #988. It does not need to be backported.
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)