Hello!
I was reading docs about HTTP compression support in -dev13 and it is a bit
unclear to me how it works.
Imagine I have:
compression algo gzip
compression type text/html text/javascript text/xml text/plain
in defaults section.
What will haproxy do if:
1) backend server does NOT support compression;
2) backend server does support compression;
3) backend server does support compression and there is no these two
compression* lines in haproxy config.
I think documentation needs to clarify things a bit.
In return, I am attaching a small patch which fixes 2 typos.
Thanks!
--- configuration.txt.orig 2012-11-22 04:11:33.000000000 +0400
+++ configuration.txt 2012-11-22 19:58:46.000000000 +0400
@@ -1887,7 +1887,7 @@
offload makes haproxy work as a compression offloader only (see notes).
The currently supported algorithms are :
- identity this is mostly for debugging, and it was useful for developping
+ identity this is mostly for debugging, and it was useful for developing
the compression feature. Identity does not apply any change on
data.
@@ -1901,7 +1901,7 @@
This setting is only available when support for zlib was built
in.
- Compression will be activated depending of the Accept-Encoding request
+ Compression will be activated depending on the Accept-Encoding request
header. With identity, it does not take care of that header.
The "offload" setting makes haproxy remove the Accept-Encoding header to
