Hi Dan, I'm using 7.18.1 with ssl support. This is all I got when I ran the code: If you will notice there is a message that says: Connection died, retrying a fresh connect. And about the other computer, same exit code but can always upload. Tried that a hundred times already. Thanks for replying. Warning: -v/--verbose overrides an earlier trace/verbose option * About to connect() to theUrl port 443 (#0) *   Trying theIPAddr... connected * Connected to theUrl (IPAddress) port 443 (#0) * SSLv3, TLS handshake, Client hello (1): } [data not shown] * SSLv3, TLS handshake, Server hello (2): { [data not shown] * SSLv3, TLS handshake, CERT (11): { [data not shown] * SSLv3, TLS handshake, Request CERT (13): { [data not shown] * SSLv3, TLS handshake, Server finished (14): { [data not shown] * SSLv3, TLS handshake, CERT (11): } [data not shown] * SSLv3, TLS handshake, Client key exchange (16): } [data not shown] * SSLv3, TLS change cipher, Client hello (1): } [data not shown] * SSLv3, TLS handshake, Finished (20): } [data not shown] * SSLv3, TLS change cipher, Client hello (1): { [data not shown] * SSLv3, TLS handshake, Finished (20): { [data not shown] * SSL connection using AES256-SHA * Server certificate: *        subject: /C=US/ST=Michigan/L=Ann Arbor/O=ADP/OU=ES/CN=theUrl *        start date: 2008-01-21 00:00:00 GMT *        expire date: 2010-01-20 23:59:59 GMT *        common name: theUrl (matched) *        issuer: /O=VeriSign Trust Network/OU=VeriSign, Inc./OU=VeriSign Interna tional Server CA - Class 3/OU=www.verisign.com/CPS Incorp.by Ref. LIABILITY LTD. (c)97 VeriSign * SSL certificate verify result: self signed certificate in certificate chain (1 9), continuing anyway. * Server auth using Basic with user 'username' > PUT /test%2Etxt HTTP/1.1 > Authorization: Basic ZmdwX3Bzb2Z0OjFBbWVyaWNh > User-Agent: curl/7.18.1 (i386-pc-win32) libcurl/7.18.1 OpenSSL/0.9.8g zlib/1.2 .3 > Host: theUrl > Accept: */* > Content-Length: 3 > Expect: 100-continue > < HTTP/1.1 200 OK < Date: Tue, 06 May 2008 23:00:00 GMT < Server: SecureTransport/4.7 * Added cookie FDX="75415136647a71397535636a50426a714444474748773d3d" for domain  theUrl, path /, expire 0 < Set-Cookie: FDX=75415136647a71397535636a50426a714444474748773d3d; path=/; Secu re < Accept-Ranges: bytes < Expires: Thu, 01 Jan 1970 00:00:00 GMT < Features: CHPWD;RTCK;STCK;ASC;DNDISP < Transfer-Encoding: chunked < Content-Type: text/plain; charset=UTF-8 < { [data not shown]   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current                                  Dload  Upload   Total   Spent    Left  Speed   0    37    0    34    0     0      4      0 --:--:--  0:00:07 --:--:--     0* Connection #0 to host theURL left intact * Re-using existing connection! (#0) with host theURL * Connected to theURL (170.146.188.96) port 443 (#0) * Server auth using Basic with user 'username' > PUT /a.dat HTTP/1.1 > Authorization: Basic ZmdwX3Bzb2Z0OjFBbWVyaWNh > User-Agent: curl/7.18.1 (i386-pc-win32) libcurl/7.18.1 OpenSSL/0.9.8g zlib/1.2 .3 > Host: theURL > Accept: */* > Cookie: FDX=75415136647a71397535636a50426a714444474748773d3d > Expect: 100-continue > * Connection died, retrying a fresh connect * Closing connection #0 * SSLv3, TLS alert, Client hello (1): * Issue another request to this URL: 'https://theURL/a.dat' * About to connect() to theURL port 443 (#0) *   Trying 170.146.188.96... connected * Connected to theURL (170.146.188.96) port 443 (#0) * SSL re-using session ID * SSLv3, TLS handshake, Client hello (1): * SSLv3, TLS handshake, Server hello (2): * SSLv3, TLS handshake, CERT (11): * SSLv3, TLS handshake, Request CERT (13): * SSLv3, TLS handshake, Server finished (14): * SSLv3, TLS handshake, CERT (11): * SSLv3, TLS handshake, Client key exchange (16): * SSLv3, TLS change cipher, Client hello (1): * SSLv3, TLS handshake, Finished (20): * SSLv3, TLS change cipher, Client hello (1): * SSLv3, TLS handshake, Finished (20): * SSL connection using AES256-SHA * Server certificate: *        subject: /C=US/ST=Michigan/L=Ann Arbor/O=ADP/OU=ES/CN=theURL *        start date: 2008-01-21 00:00:00 GMT *        expire date: 2010-01-20 23:59:59 GMT *        common name: theURL (matched) *        issuer: /O=VeriSign Trust Network/OU=VeriSign, Inc./OU=VeriSign Interna tional Server CA - Class 3/OU=www.verisign.com/CPS Incorp.by Ref. LIABILITY LTD. (c)97 VeriSign * SSL certificate verify result: self signed certificate in certificate chain (1 9), continuing anyway. * Server auth using Basic with user 'username' > PUT /a.dat HTTP/1.1 > Authorization: Basic ZmdwX3Bzb2Z0OjFBbWVyaWNh > User-Agent: curl/7.18.1 (i386-pc-win32) libcurl/7.18.1 OpenSSL/0.9.8g zlib/1.2 .3 > Host: theURL > Accept: */* > Cookie: FDX=75415136647a71397535636a50426a714444474748773d3d > Expect: 100-continue > * Empty reply from server * Connection #0 to host theURL left intact curl: (52) Empty reply from server * Closing connection #0 * SSLv3, TLS alert, Client hello (1):   ----- Original Message ---- From: Dan Fandrich <dan@coneharvesters.com> To: curl-users@cool.haxx.se Sent: Tuesday, May 6, 2008 11:41:29 PM Subject: Re: Upload Misbehaving On Tue, May 06, 2008 at 07:32:31AM -0700, von wrote: > I was able to run curl and upload a file to a webserver through https. I tried > to do the same on another machine, using the same curl/libcurl I used from the > previous machine, but it didn't worked, the file was not uploaded. >  > On both machines I receive the exit code 52: The server didn¢t reply anything, > which here is considered an error. But take note that one uploaded and the > other didn't. I have windows xp sp2 on both machines and I even tried to sniff > curl and compared the files used. Both machines are using the same files (dlls) > and same version. >  > Could someone point me in the right direction where to start looking for this > weird problem? If you are getting an error code in both cases, it's probably sheer luck that one of them actually completes the upload.  What version of curl are you using?  Can you post the debug output you get with the -v option? >>> Dan -- http://www.MoveAnnouncer.com              The web change of address service           Let webmasters know that your web site has moved ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
Received on 2008-05-07