Opened 19 years ago
Last modified 15 years ago
#2128 closed Feature request
Stopping server connect before LIST should disconnect
|Reported by:||Scott M. Sanders||Owned by:|
|Keywords:||Cc:||Scott M. Sanders, Tim Kosse, Alexander Schuch|
|Component version:||Operating system type:|
|Operating system version:|
In the FileZilla client, when a user attempts to
connect to a server, if the user aborts the connection
before or during the LIST command, FileZilla should
disconnect from the server. The user most likely wants
to cancel connecting to the server entirely. Also,
without the remote file/folder list, there is little
the user can do (without manually refreshing the remote
list, which requires such intuition) except upload to
the default remote folder or enter raw FTP commands.
Change History (2)
comment:1 by , 15 years ago
comment:2 by , 15 years ago
My point four years ago was I think that when connecting, if the user clicks Stop/Cancel before LIST completes, it should not stay connected because I think FileZilla is geared more to the intermediate user, and without a remote list, I think many users (like myself) would find being technically but not visibly connected, and without a nice warning ("LIST canceled. Retry or disconnect?"), to be a bit pointless.
Rejected. If LIST gets sent, the client is already connected. Aborting the listing should not disconnect, that would make cancel logic highly unintuitive.