cURL / Mailing Lists / curl-users / Single Mail

curl-users

Post of large files over ssl

From: Christian Meynert <c_meynert_at_web.de>
Date: Tue, 23 Oct 2001 15:00:17 +0200

Hi!

I use curl 7.9 (win32) libcurl 7.9 (OpenSSL 0.9.6b), in order to post files over ssl. The HTTPS POST requests don't complete, when I try to transfer more than 44KB. They just freeze and no reasonable message is shown.

I use a command like follows:

curl -v -E x:\cert\clientcertificate.pem:pwdtest --user Donald:Duck --data-ascii @x:\data\out.xml https://....

The curl output looks like this:
* Connection (#0) left alive
* Closing live connection (#0)

I found out, that the transfer works fine, if I don't utilize the client certificate within the call.

Is it possible to use client certificates within a call for a POST request over HTTPS? Does anybody has an idea for the reason of this problem?

The access log of the (reverse) proxy shows the HTTP/1.1 error code "403".

It looks as follows:
10.84.145.117 - - [22/Oct/2001:12:24:22 +0200] "POST /XX/XX/XXX.jhtml HTTP/1.1" 403 252 "-" "curl/7.9 (win32) libcurl 7.9 (OpenSSL 0.9.6b)"

The error log of the (reverse) proxy has the following entries:

[Mon Oct 22 14:44:30 2001] [error] mod_ssl: Re-negotiation handshake failed: Not accepted by client!?
[Mon Oct 22 14:44:30 2001] [error] mod_ssl: SSL error on writing data (OpenSSL library error follows)
[Mon Oct 22 14:44:30 2001] [error] OpenSSL: error:140940F5:SSL rou-tines:SSL3_READ_BYTES:unexpected record
[Mon Oct 22 14:44:30 2001] [info] [client 10.84.145.117] client stopped connection before rflush completed

_______________________________________________________________________
1.000.000 DM gewinnen - kostenlos tippen - http://millionenklick.web.de
IhrName@web.de, 8MB Speicher, Verschluesselung - http://freemail.web.de
Received on 2001-10-23