ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 27437] - FTP "get" and "list" tasks fail
Date Tue, 09 Mar 2004 01:27:42 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=27437>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=27437

FTP "get" and "list" tasks fail





------- Additional Comments From scohen@apache.org  2004-03-09 01:27 -------
Antoine is basically correct.  There is (currently) no support for this ftp format in commons.net.
 
The format is CLOSE TO but not identical to the Standard unix ftp server list format that
is the 
default in commons-net. 
 
Here is a typical unix ftp standard listing followed by one of yours: 
-rwxr-xr-x   2 root     root         4096 Mar  2 15:13 zxbox 
-rw-r-----   1 ravensm  sca         9280 02 Mar 16:27 ZMRPC963.m 
 
Clearly, the problem seems to be one of locale (reversal of the month and day fields).  The

standard unix ftp parser is the default in commons-net and the format on your server is 
confusing the parser. 
 
The basic problem is that the FTP specification (RFC959) defines the FTP listing format in
a 
very loose way.  The protocol was intended for manual scanning by a user and definitely not

for automation purposes.  Similar problems crop up with servers in other languages such as
a 
German one that might use the abbreviation okt for october, etc. 
 
I have never heard this complaint about unix servers in non-American locales, but I have heard

it about AIX servers.  We could write a parser that expected your format, but I have a feeling
it 
would break American AIX ftp servers. 
 
Additionally, commons-net is moving toward an autodetection scheme for ftp server types. 
It 
does a pretty good job telling NT servers from Unix ones, but your situation brings up a new

wrinkle.  Which locale should a parser assume for a server if there is no way to make the

server define its listing format?  Assuming there is some way to differentiate AIX ftp servers

from Unix ones in an automated fashion, we would have to come up with a way of 
differentiating the date-format locales as well, and I'm not sure that's possible. 
 
It's a real mess, frankly, due to the vagueness of the ftp spec on this matter.  As a committer

for commons-net, I would be willing to work with you to get this resolved, but I need your
input 
and that of other aix ftp server users to determine the RIGHTway to solve this problem.  I
am 
guessing that the problem is not very widespread, or we would have heard many more 
complaints about this.  The more instances we can get of this pattern the more likely it will
be 
to be solved. 
 
However, it's totally out of Ant's hands to be able to fix this.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message