Red Hat Bugzilla – Bug 145699
gFTP should not disconnect on 4xx return code from server
Last modified: 2013-04-02 00:20:35 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5)
Description of problem:
Not every ftp server has a default working directory upon logon.
When gFTP connects and logs on it issues a PWD command.
When there is no default working directory, gFTP sees return code 450
and promptly disconnects, saying it will try again 30 seconds.
This is wrong. gFTP should remain connected, and allow the user to use
the drop down menus to manually change directory.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. ftp to: sruvm.sru.edu
Actual Results: Looking up sruvm.sru.edu
Connected to sruvm.sru.edu:21
220-FTPSERVE IBM VM V2R4 at SRUVM.SRU.EDU, 12:59:21 EST THURSDAY 01/20/05
220 Connection will close if idle for more than 5 minutes.
230-ANONYMOU logged in; no working directory defined
230 File pool SERVER5 unavailable or unknown;
215-VM/ESA Version 2 Release 3.0, service level 9902
VM/CMS Level 14, Service Level 902
215 VM is the operating system of this server.
200 Representation type is IMAGE.
450 No current working directory defined
Invalid response '4' received from server.
Disconnecting from site sruvm.sru.edu
Waiting 30 seconds until trying to connect again
Expected Results: gFTP should have left well enough alone and stayed
connected after getting the 450 from the PWD command.
I'm setting this as "high severity", not because it crashes etc, but
because it diminshes the usefulness of the program... there's no way
to effectively use the ftp server if the server doesn't have a default
4xx erros from FTP means the condition is temporary and may be tried
again..... so gFTP must not disconnect from the server in those cases.
*** This bug has been marked as a duplicate of 145711 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.