LIST bug

[cyberduck]

a415900 created the issue

According to RFC959, the command list has 1 optional arguement: pathname. Cyberduck appends the option "-a" to the list command, eg "LIST -a". Unless there is a newer RFC that says otherwise, this behaviour is incorrect.

Error message from JFTP:

2008-01-17 09:40:58 FTP 10.32.32.193 1651422152  Command: LIST -a Error: No such file or directory

[cyberduck]

@dkocher commented

It should fallback to use the plain "LIST" command if "LIST -a" fails. Does it not? We use the -a option because many servers do not return files with a leading "." otherwise.

[cyberduck]

e1605f3 commented

It doesnt fallback to plain "LIST" when "LIST -a" fails... I have the newest version...

250 Ok PASV 227 Entering Passive Mode (213,179,58,81,123,15) LIST -a 150 Accepted data connection 500 No such file or directory

Replying to [comment:1 dkocher]:

It should fallback to use the plain "LIST" command if "LIST -a" fails. Does it not? We use the -a option because many servers do not return files with a leading "." otherwise.

[cyberduck]

d7cc93e commented

didn't an earlier version contain an option to UN check the box to send a "List-a" command??

[cyberduck]

@dkocher commented

Replying to [comment:3 theodorouj@cadmus.com]:

This is no more an option in the Preferences as it is supposed to fallback on failure. You can still set the option using Terminal.app with

defaults write ch.sudo.cyberduck ftp.sendExtendedListCommand false

[cyberduck]

57da35c commented

It is not falling back, specifically when talking to MassTransit servers (in my case). Can we add this option back, as well as keep the "failback"?

[cyberduck]

@dkocher commented

In 879e42548a95c348cfc3ea12bd1912108b0b8ad4.