Attached please find a patch for bypassing libcurl's native handling of
chunked transfer-encoding (HTTP_TRANSFER_ENCODING_RAW) and of non-identity
content-encoding (HTTP_CONTENT_ENCODING_RAW). Passing a non-zero value on
either of these option (of course using the standard curl_easy_setopt
mechanism) will cause libcurl to pass the raw body data to the application.
In the case of chunked transfer encoding libcurl will still process the data
(to detect when the connection should be closed), but will not pass the
processed data to the application.

Note that while one is able to bypass the later (content-encoding inflating)
by NOT setting the ENCODING option, I choose to include a way to
specifically override the default libcurl handling, as users may actually
want to make use of the ENCODING option without letting curl to inflate the
content.

I hope this change will find its way into the main libcurl development line.

Cheers,
Shmul