From: Baptiste Assmann <bedis9@gmail.com>
Date: Sat, 5 Jan 2013 14:44:44 +0000 (+0100)
Subject: DOC: typo and minor fixes in compression paragraph
X-Git-Tag: v1.5-dev18~133
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=650d53d839d1f0c51a572d7fe0158e29d35edfdf;p=thirdparty%2Fhaproxy.git

DOC: typo and minor fixes in compression paragraph
---

diff --git a/doc/configuration.txt b/doc/configuration.txt
index 035da780cb..5117404cb8 100644
--- a/doc/configuration.txt
+++ b/doc/configuration.txt
@@ -1926,15 +1926,23 @@ compression offload
   then be used for such scenarios.
 
   Compression is disabled when:
-    * the server is not HTTP/1.1.
+    * the request does not advertise a supported compression algorithm in the
+      "Accept-Encoding" header
+    * the response message is not HTTP/1.1
     * HTTP status code is not 200
-    * requests does not contain Transfer-Encoding: chunked or Content-Length.
-    * Content-Type is multipart
-    * the request contains "Cache-control: no-transform".
-    * User-Agent matches "Mozilla/4" except MSIE 6 with XP SP2, or MSIE 7 and later.
-    * The response is already compressed (see compression offload).
-
-  The compression does not rewrite Etag headers
+    * response contain neither a "Content-Length" header nor a
+      "Transfer-Encoding" whose last value is "chunked"
+    * response contains a "Content-Type" header whose first value starts with
+      "multipart"
+    * the response contains the "no-transform" value in the "Cache-control"
+      header
+    * User-Agent matches "Mozilla/4" unless it is MSIE 6 with XP SP2, or MSIE 7
+      and later
+    * The response contains a "Content-Encoding" header, indicating that the
+      response is already compressed (see compression offload)
+
+  Note: The compression does not rewrite Etag headers, and does not emit the
+        Warning header.
 
   Examples :
         compression algo gzip