On Tue, 2 Dec 2003, Gisle Vanem wrote:

> > ... which makes curl connect to a FTP server as normal, then issue the
> > magic commands that "converts" it to a SSL-using connection.
>
> That works until it's starting (or ending?) the transfer:
>
> 0000: PASV
> 0000: 227 Entering Passive Mode (195,56,193,26,128,18)
> == Info: About to connect() to 195.56.193.26 port 32786
> == Info: Connecting to cable-193-26.szhalomb.fibernet.bacs-net.hu (195.56.193.26) port 32786
> == Info: Connected the data stream with PASV!

[snip]

> 0000: RETR .bashrc
> 0000: 150 Opening BINARY mode SSL data connection for .bashrc (1263 bytes)

[snip]

> It connects to his port 32786 okay, but the file isn't transferred AFAICS.
> Hard to say because it's a tiny 1263 byte file.

Are you sure the server assumes a non-SSL data connection in this case? I mean
is libcurl doing the proper connection?

> Note the 195.56.193.26 machine didn't send a FIN. So maybe it is curl who
> should close first?

No, when speaking FTP the sending end signals end of file by closing the
connection. But the file isn't sent at all here, is it?

-- 
    Daniel Stenberg -- http://curl.haxx.se/ -- http://daniel.haxx.se/
 [[ Do not post private mails to this email address. They won't reach me. ]]
-------------------------------------------------------
This SF.net email is sponsored by OSDN's Audience Survey.
Help shape OSDN's sites and tell us what you think. Take this
five minute survey and you could win a $250 Gift Certificate.
http://www.wrgsurveys.com/2003/osdntech03.php?site=8