Hi,
Bernhard R. Link wrote:
Peskiness: critical
:-D
uscan does active ftp by default on ftp:// URLs. While this can be
overriden in the watch file and allegdly via some environment
_Configuration file_ variable rather than environment. It's not allegedly
either, it's in both the default config file and uscan(1) :-)
variable, it is no sane default since the days firewalls, NATs and
hosts with multiple IP addresses were invented.
uscan doesn't actually use either active or passive FTP by default, having
read the code. It uses Net::FTP and if you don't explicitly specify that
active or passive should be used then Net::FTP makes its own mind up.
From Net::FTP(3perl):
" Passive - If set to a non-zero value then all data transfers will
be done using passive mode. This is not usually required except
for
some dumb servers, and some firewall configurations. This can
also
be set by the environment variable "FTP_PASSIVE".
"
Even worse, when this fails, it does not even output an error message.
Even using --verbose --debug you only get:
> uscan debug: received content:
> [End of received content]
while the ftp server is actually sending errors:
> read(4, "500 Illegal PORT command.\r\n", 1024) = 27
As far as I can see, this means that Net::FTP and/or LWP is claiming that
the request was successful.
I've uploaded a small test script to
http://alioth.debian.org/~adam-guest/ftptest.pl - could you please run it
against the ftp site you were using uscan with and let me know the result?
Regards,
Adam
--
To unsubscribe, send mail to [EMAIL PROTECTED]
