curl-library
Transfer-Encoding
Date: Mon, 18 Apr 2011 19:59:51 +0200 (CEST)
Hi friends,
I've just now pushed a series of changes that introduce support for compressed
HTTP Transfer-Encoding.
CURLOPT_TRANSFER_ENCODING is the option to set to enable it and right now we
can only set it to 1 to ask for gzip compression or 0 to not ask for
compression. I'm interested to hear if anyone can think of good reasons to
specificly ask for other or multiple compression algorithms (like deflate).
Compressed Transfer-Encoding is similar to the existing Content-Encoding
approach that we support, with the exception that automatic uncompression when
receiving data was always meant to be done on transfer-encoding and not on the
actual content (content-encoding) so the current practise has always been a
little off.
I have an almost completed 700+ word piece I intend to post on my blog[1]
within a day or so with further details and explanations if you're interested.
[1] = http://daniel.haxx.se/blog/
-- / daniel.haxx.se ------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.htmlReceived on 2011-04-18