Hi Daniel We also built libcurl to use WinSSL, and re-ran the tests with no proxy case:
Here are the libcurl debugging traces. Looks like it is still being rejected by the web server. Seems like there is a length issue? GET /xxx/xxxxx/ HTTP/1.1 Host: xxxx.com User-Agent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.101 Safari/537.36 Accept: */* Accept-Encoding: deflate, gzip schannel: client wants to read 16384 bytes schannel: encdata_buffer resized 17408 schannel: encrypted data buffer: offset 0 length 17408 schannel: encrypted data got 8980 schannel: encrypted data buffer: offset 8980 length 17408 schannel: decrypted data length: 1 schannel: decrypted data added: 1 schannel: decrypted data cached: offset 1 length 16384 schannel: encrypted data length: 8943 schannel: encrypted data cached: offset 8943 length 17408 schannel: decrypted data length: 322 schannel: decrypted data added: 322 schannel: decrypted data cached: offset 323 length 16384 schannel: encrypted data length: 8586 schannel: encrypted data cached: offset 8586 length 17408 schannel: decrypted data length: 1 schannel: decrypted data added: 1 schannel: decrypted data cached: offset 324 length 16384 schannel: encrypted data length: 8549 schannel: encrypted data cached: offset 8549 length 17408 schannel: decrypted data length: 8515 schannel: decrypted data added: 8515 schannel: decrypted data cached: offset 8839 length 16384 schannel: encrypted data buffer: offset 0 length 17408 schannel: decrypted data buffer: offset 8839 length 16384 schannel: schannel_recv cleanup schannel: decrypted data returned 8839 schannel: decrypted data buffer: offset 0 length 16384 HTTP/1.1 200 OK content-length: 8516 content-type: text/html date: Mon, 26 Oct 2015 09:49:07 GMT p3p: CP="NON CUR OTPi OUR NOR UNI" server: WebSEAL/6.1.1.19 (Build 150525) pragma: no-cache cache-control: no-cache Added cookie PD-S-SESSION-ID="0_276uA0mI/xtI7N/ge/sN8IByZLvZkS/CPnoKBJaMBS6z9s03sWU=" for domain ept.bursamalaysia.com, path /, expire 0 Set-Cookie: PD-S-SESSION-ID=0_276uA0mI/xtI7N/ge/sN8IByZLvZkS/CPnoKBJaMBS6z9s03sWU=; Path=/; Secure no chunk, no close, no size. Assume close to signal end ** we dumped out the HTML content received, seems ok. <html> <HEAD> <TITLE>Login</TITLE> <meta http-equiv="Cache-Control" content="no-store, no-cache, must-revalidate"/> <meta http-equiv="Cache-Control" content="post-check=0, pre-check=0"/> <meta http-equiv="pragma" content="no-cache"> <meta http-equiv="Expires" content="Sat, 6 May 1995 12:00:00 GMT"/> bla bla bla </html> ** the continuing debugging traces as follows schannel: client wants to read 16384 bytes schannel: encrypted data buffer: offset 0 length 17408 schannel: Curl_read_plain returned CURLE_RECV_ERROR schannel: encrypted data buffer: offset 0 length 17408 schannel: encrypted data buffer: offset 0 length 17408 schannel: decrypted data buffer: offset 0 length 16384 schannel: schannel_recv cleanup Closing connection 0 schannel: shutting down SSL/TLS connection with ept.bursamalaysia.com port 443 Send failure: Connection was reset schannel: failed to send close msg: Failed sending data to the peer (bytes written: -1) schannel: clear security context handle schannel: decremented credential handle refcount = 0 ** at this point, our code logged a CURL error message "WebCDS error Failure when receiving data from the peer" Please note that the same GET /xxx/xxxxx/ HTTP/1.1 under OpenSSL 1.0.2d did not have the same error. Under OpenSSL, the error occurred at a later HTTP interaction. I am hopelessly lost. Pleas help. Regards KS ------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
