aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorIsaac Boukris <iboukris@gmail.com>2016-04-23 15:52:04 +0300
committerDaniel Stenberg <daniel@haxx.se>2016-05-01 23:27:01 +0200
commit7987f5cb14dc2fae5921ac3a2989a7d0e51474d2 (patch)
tree91edaa028fbf2efe2f3e24f02fa41505309f0f2a
parent9291e2b9d0a5975d7d6b0fe2a0a45119724c75c3 (diff)
CURLOPT_ACCEPT_ENCODING.3: Follow-up clarification
Mention possible content-length mismatch with sum of bytes reported by write callbacks when auto decoding is enabled. See #785
-rw-r--r--docs/libcurl/opts/CURLOPT_ACCEPT_ENCODING.37
1 files changed, 4 insertions, 3 deletions
diff --git a/docs/libcurl/opts/CURLOPT_ACCEPT_ENCODING.3 b/docs/libcurl/opts/CURLOPT_ACCEPT_ENCODING.3
index 3d172dcbe..c31263139 100644
--- a/docs/libcurl/opts/CURLOPT_ACCEPT_ENCODING.3
+++ b/docs/libcurl/opts/CURLOPT_ACCEPT_ENCODING.3
@@ -54,9 +54,10 @@ Servers might respond with Content-Encoding even without getting a
Accept-Encoding: in the request. Servers might respond with a different
Content-Encoding than what was asked for in the request.
-The Content-Length: servers send for a compressed response is supposed to be
-for the compressed content but sending the size for the non-compressed version
-of the resource is a very common mistake.
+The Content-Length: servers send for a compressed response is supposed to
+indicate the length of the compressed content so when auto decoding is enabled
+it may not match the sum of bytes reported by the write callbacks (although,
+sending the length of the non-compressed content is a common server mistake).
.SH DEFAULT
NULL
.SH PROTOCOLS