cURL / Mailing Lists / curl-library / Single Mail

curl-library

Re: CURLOPT_ENCODING | Problem with deflate

From: Michael Hecker <Hecker.Michael_at_gmx.de>
Date: Tue, 26 Feb 2008 14:44:31 +0100

Michael Hecker schrieb:
> Hello,
> I'm using gzip compression without any problems, but "deflate" is
> problematical.
>
> When I'm using
> curl_easy_setopt(curl_handle, CURLOPT_ENCODING, "deflate");
> I get the following error.
>
> INFO: About to connect() to www.anyserver.com port 443
> INFO: Trying xxx.xxx.192.10...
> INFO: connected
> INFO: Connected to www.anyserver.com (xxx.xxx.192.10) port 443
> INFO: successfully set certificate verify locations:
> INFO: CAfile:
> C:\Project\libcurl\VisualStudio\MyApplication\Release\cacert.pem
> CApath: none
> INFO: SSLv2, Client hello (1):
> INFO: SSLv3, TLS handshake, Server hello (2):
> INFO: SSLv3, TLS handshake, CERT (11):
> INFO: SSLv3, TLS handshake, Server finished (14):
> INFO: SSLv3, TLS handshake, Client key exchange (16):
> INFO: SSLv3, TLS change cipher, Client hello (1):
> INFO: SSLv3, TLS handshake, Finished (20):
> INFO: SSLv3, TLS change cipher, Client hello (1):
> INFO: SSLv3, TLS handshake, Finished (20):
> INFO: SSL connection using RC4-MD5
> INFO: Server certificate:
> INFO: subject: XXXXXXXXXXX
> INFO: start date: 2006-03-30 11:35:48 GMT
> INFO: expire date: 2008-03-29 11:35:48 GMT
> INFO: common name: *.anyserver.com (matched)
> INFO: issuer:XXXXXXXXXXXXX
> INFO: SSL certificate verify ok.
> INFO: Added cookie ASP.NET_SessionId="fveio555ysfkzsj3mdjwr53d" for
> domain www.anyserver.com, path /, expire 0
> INFO: Error while processing content unencoding: incorrect header check
> INFO: Failed writing data
> INFO: Closing connection #0
> INFO: SSLv3, TLS alert, Client hello (1):
> INFO: failed writing received data to disk/application
>
> Could you explain (INFO: Error while processing content unencoding:
> incorrect header check) to me?
>
> Thank you very much!
>
> Michael
>
Hey,
I just found this thread
(http://curl.haxx.se/mail/lib-2005-12/0021.html), which answers my question.
It seems as if IIS responds with glib encoded data and curl expects zlib
encoded data.

Thanks,
Michael
Received on 2008-02-26