summaryrefslogtreecommitdiff
path: root/docs/INTERNALS.md
diff options
context:
space:
mode:
authorPatrick Monnerat <patrick@monnerat.net>2017-11-05 15:09:48 +0100
committerPatrick Monnerat <patrick@monnerat.net>2017-11-05 15:09:48 +0100
commitdbcced8e32b50c068ac297106f0502ee200a1ebd (patch)
tree0fa1ce28f33ab968792e21264e9a9318807d9f9b /docs/INTERNALS.md
parent462f3cac34c09b9c28b449258e71dc37171dc604 (diff)
downloadcurl-dbcced8e32b50c068ac297106f0502ee200a1ebd.tar.gz
HTTP: support multiple Content-Encodings
This is implemented as an output streaming stack of unencoders, the last calling the client write procedure. New test 230 checks this feature. Bug: https://github.com/curl/curl/pull/2002 Reported-By: Daniel Bankhead
Diffstat (limited to 'docs/INTERNALS.md')
-rw-r--r--docs/INTERNALS.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/INTERNALS.md b/docs/INTERNALS.md
index 6c1d5baf2..fb9d50378 100644
--- a/docs/INTERNALS.md
+++ b/docs/INTERNALS.md
@@ -673,7 +673,7 @@ Content Encoding
where string is the intended value of the Accept-Encoding header.
- Currently, libcurl does not support multiple encodings and only
+ Currently, libcurl does support multiple encodings but only
understands how to process responses that use the "deflate" or "gzip"
Content-Encoding, so the only values for [`CURLOPT_ACCEPT_ENCODING`][5]
that will work (besides "identity," which does nothing) are "deflate"