You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With a user supplied IP where there is no host at that IP, ftp.auth() takes a long time to throw ETIMEDOUT. Using the following code, on OS X I tested to a local IP with no device at that address. It took about 80 seconds to timeout. Shouldn't it be much less? I'm thinking 4-5 seconds (in terms of enduser patience until their mistake is evident).
var os = require("os"),
fs = require("fs"),
JSFtp = require("jsftp");
var HOST = '192.168.0.99';
var PORT;
var USER = 'tim';
var PWD = 'blah';
var ftp = new JSFtp({
host: HOST
});
// connect to remote
ftp.auth(USER, PWD, function (err, data) {
if (err) {
console.log('Failed to connect to remote: ' + err);
return;
}
// emit connect
console.log('Connected ' + data.text);
ftp.raw.quit(function (err, data) {
console.log('quit:' + data);
});
});
The text was updated successfully, but these errors were encountered:
With a user supplied IP where there is no host at that IP, ftp.auth() takes a long time to throw ETIMEDOUT. Using the following code, on OS X I tested to a local IP with no device at that address. It took about 80 seconds to timeout. Shouldn't it be much less? I'm thinking 4-5 seconds (in terms of enduser patience until their mistake is evident).
The text was updated successfully, but these errors were encountered: