On Mon, 10 Mar 2003, Dechnik, Michael wrote:

> It appears that we cannot post a document to a remote b2b server using
> curl. We contiuously get the the same error: curl: (52) Empty reply from
> server. We have tried several command line options including the -2, -3
> --trace. It appears that a certificate exchange is completed then the post
> ends prematurely based on the trace file. Any thoughts?

I've seen servers do this when they don't like your client certificate. I.e,
they don't allow you to do the SSL connection.

I'd say that only the server logs of the server you're operating against can
provide the full answer here.

-- 
 Daniel Stenberg -- curl, cURL, Curl, CURL. Groks URLs.
-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open! 
Get cracking and register here for some mind boggling fun and 
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en