Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
inoxia created the issue
Cyberduck 2.7.2 (2750)/2750 doesn't list directories on some WinNT based servers anymore. This used to work...
Example:
ftp://cyberduck:cyber@ftp.electric.se
Cyberduck 2.7.2 lists nothing in this directory.
Using OS X FTP client (Terminal) ls command lists the contents correctly:
ftp> ls 500 'EPSV': command not understood 227 Entering Passive Mode (87,253,81,67,169,121). 125 Data connection already open; Transfer starting. 09-04-06 11:28AM 149 gearkommandon with spaces.txt 09-04-06 11:28AM 149 gearkommandon with umlauts ???.txt 09-04-06 11:28AM 149 gearkommandon.txt
Thanks for your great work with Cyberduck!!!
/Nils Fridén Stockholm, Sweden
The text was updated successfully, but these errors were encountered:
d8552e4 commented
Having this same problem with an SFTP server running on Win2K3, which presents the same format output in command-line SFTP.
Oddly, this worked for me in 2.7.2 but not in 2.7.3.
Sorry, something went wrong.
Should I open a separate bug since my issue is occurring with SFTP rather than FTP? Or should I just change the component for this bug?
Changing component back to FTP... didn't mean to reset it for that comment, since the original post does regard FTP... argh, I'm making a mess of this.
@dkocher commented
Testcase added in 81cb2a5.
dkocher
No branches or pull requests
cyberduck commentedFeb 1, 2007
Cyberduck 2.7.2 (2750)/2750 doesn't list directories on some WinNT based servers anymore. This used to work...
Example:
ftp://cyberduck:cyber@ftp.electric.se
Cyberduck 2.7.2 lists nothing in this directory.
Using OS X FTP client (Terminal) ls command lists the contents correctly:
Thanks for your great work with Cyberduck!!!
/Nils Fridén
Stockholm, Sweden
The text was updated successfully, but these errors were encountered: