mirror of
https://github.com/curl/curl.git
synced 2026-08-25 10:03:37 +03:00
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
This commit is contained in:
parent
462f3cac34
commit
dbcced8e32
11 changed files with 736 additions and 283 deletions
|
|
@ -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"
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue