After a timeout, WS_FTP Server sends the following spontaneous reply "500 connection timed out" before closing the connection.
WS_FTP client, upon issuing the next command after the timeout, will receive and display the server's timeout response, whatever it may be. It is probably not a good idea to rely on a specific FTP code or specific information being in the timeout error message. WS_FTP does not even rely on getting a timeout error message at all. What WS_FTP does expect is that the connection will be closed and any subsequent commands on that connection will fail. WS_FTP does attempt to automatically reconnect when it senses the connection is dead, navigates back to the same location if necessary and possible, and retries the command with the new connection. --Claude Edwards --WS_FTP Team. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Liu, Hong Sent: Tuesday, August 13, 2002 9:19 PM To: '[EMAIL PROTECTED]' Cc: Liu, Hong Subject: [WS_FTP Forum] 421 for connection timeout Hi, all, I am a newcomer to this list. I have a very specific question about WS_FTP (or any existing FTP) implementation regarding the server procedure when closing down a conneciton due to timeout (i.e., client inactivity). I am hoping that FTP implementors on this list will be able to help me out. My understanding is that when timeout occurs, the server will send a (unsolicited response) message to the client with result code 421 and the timeout value (say 900 seconds), before closing down the control connection. Is this what WS_FTP has implemented? Is this also a common practice by other FTP implementations? How can I find out those information? Please respond to me in private if this is not of general interests to the list. Thanks in advance! --Hong Please visit http://www.ipswitch.com/support/mailing-lists.html to be removed from this list. Please visit http://www.ipswitch.com/support/mailing-lists.html to be removed from this list.
