From: Baptiste Assmann Date: Mon, 21 Dec 2015 16:57:32 +0000 (+0100) Subject: DOC: compression: missing mention of libslz for compression algorithm X-Git-Tag: v1.7-dev2~170 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=f085d6309986e7119db36f366877b8b57f275530;p=thirdparty%2Fhaproxy.git DOC: compression: missing mention of libslz for compression algorithm Compression algorithm documentation only mention zlib, while HAProxy also support libslz, which is much lighter and faster. --- diff --git a/doc/configuration.txt b/doc/configuration.txt index 4fe410f32a..b384b7b4aa 100644 --- a/doc/configuration.txt +++ b/doc/configuration.txt @@ -2501,14 +2501,14 @@ compression offload data. gzip applies gzip compression. This setting is only available when - support for zlib was built in. + support for zlib or libslz was built in. deflate same as "gzip", but with deflate algorithm and zlib format. Note that this algorithm has ambiguous support on many browsers and no support at all from recent ones. It is strongly recommended not to use it for anything else than experimentation. This setting is only available when support - for zlib was built in. + for zlib or libslz was built in. raw-deflate same as "deflate" without the zlib wrapper, and used as an alternative when the browser wants "deflate". All major @@ -2517,7 +2517,7 @@ compression offload and some versions of Safari. Do not use it in conjunction with "deflate", use either one or the other since both react to the same Accept-Encoding token. This setting is only - available when support for zlib was built in. + available when support for zlib or libslz was built in. Compression will be activated depending on the Accept-Encoding request header. With identity, it does not take care of that header.