Hi, The transfer encoding chunked header tells you that your server's response will be sent in more than one little pieces. Sometimes the server does so, sometimes not. Depends on the response and on whether the server knows the response's length in the very moment it starts sending it. So you should detect the transfer encoding chunked header and modify your client's behavior by trying to read server data uintil the server tells you that the response is complete. How this is done, you'll find in the RFC fpor HTTP 1.1 . It is not an SSL issue. HTH Z.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Vinu Thomas Sent: Dienstag, 3. Oktober 2006 13:01 To: openssl-users@openssl.org Subject: Transfer Encoding : Chunked Hi All, I am implementing an HTTP 1.1 client in C++ using openssl for SSL. Sometimes the Http response I get back says that the Transfer Encoding : chunked I really donot do anything extra here in this case. As usual I do a SSL_Pending to see if any data is pending in the SSL buffer and if not finish reading. To further elaborate I am implementing a WebServices client in C++. The problem is sometimes the binary data in some of the Soap XML tags are complete and sometimes they are not. Although a similar tool written in java seems to work fine. Am I missing something here or is what I am doing ok. Thanks Vinu ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
smime.p7s
Description: S/MIME Cryptographic Signature
