I'm using the callback function to receive the content and process it
myself. It seems that libcurl automatically decodes the chunked encoding
and does not return the content in the "raw" form. In my program the
consistency between the received header and the content is crucial. The
received header still contains "transfer-encoding: chunked" and no content
length but the received content does not contain the chunked encoding
anymore.

Is this the intentional behavior of libcurl or am I just doing someting
wrong? Is there a way to get the raw content of a transfer to process it
afterwards? I guess I can force HTTP 1.0 in order to get rid of the chunked
encoding stuff but that's only a workaround.

Best regards,

Cyrill

-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge
Received on 2003-05-27