New Era wrote:
So inserting a high value into PasvPortRange may be a
solution(start 16384 and PasvPortRange= 4), but if
other applications randomly uses ports
in this range, what will be the behaviour of the
ftpserver I mean, if x application uses port 1 and
when ftpserver also wants
Hello all,
Could someone tell me where I can find some source or tutorial about
the http user authentication? It would be best in connection with
httpsrv component of course :-)
with best regards
Igor
--
To unsubscribe or change your settings for TWSocket mailing list
please goto
Thanks Wilfred, but I need to send the next message only after I receive the
ok from server.
Wilfried Mestdagh wrote:
Hello Larini,
I'm getting unstable times, from 70 ms to 3 seconds.
This can happen. It is depending the traffic on the network. If very
heavy on a large network it _can_
I'm having a problem with the Ftpcli component (V2.99 D5).
99 times out of 100 the quit command works correctly, but on the other
time FTPClient1.Quit returns false.
Please try using FtpCli v2.100 or later (beta dated September 2005 or
later), it contains a fix for a problem uploading small
David Rose wrote:
(sorry if you already got this - I didn't get an auto-acknowledgment from
the list, so I don't know if it was posted).
I'm having a problem with the Ftpcli component (V2.99 D5).
I'm uploading several files to an FTP site, at the end of each upload I
use the following
99 times out of 100 the quit command works correctly, but on the other
time FTPClient1.Quit returns false. The time between the two codesite
messages is about 300ms, so I'm presuming that it's not due to a time
out.
What else can result in this function returning false so quickly ?
Please try using FtpCli v2.100 or later (beta dated September 2005 or
later), it contains a fix for a problem uploading small files, and the
problem may have caused other issues
Thanks, same problem. It seems that the error is
500 Control connection closed. Connection aborted (Winsock error
