Bug 18108 - [TM FTP] client must turn off ftp messages
Summary: [TM FTP] client must turn off ftp messages
Status: RESOLVED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P4 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-VCM-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: readme
: 18401 (view as bug list)
Depends on:
Blocks:
 
Reported: 2002-05-28 16:23 EDT by Jean-Michel Lemieux CLA
Modified: 2005-05-06 16:16 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jean-Michel Lemieux CLA 2002-05-28 16:23:08 EDT
build 0527
if you don't turn off ftp server messages at the end of the transfer you may
receive a summary message, or an introduction message. This will result in the
ftp client throwing an exception when nothing wrong has happened. It is
confusing because most of the time the transfer was successful.

================ This was shown in an error dialog after performing a get ======

You have transfered XXX bytes
221 - Total traffic for this session
221 - Thank you for using the ftp server at XXXX
221 Goodbye
Comment 1 Michael Valenta CLA 2002-05-28 17:08:40 EDT
I get the messages all the time with no exception being thrown (observed using 
tracing). Are you using passive mode?
Comment 2 Jean-Michel Lemieux CLA 2002-05-31 06:07:34 EDT
*** Bug 18401 has been marked as a duplicate of this bug. ***
Comment 3 Jean-Michel Lemieux CLA 2002-05-31 06:08:36 EDT
I'm not using passive mode. But this is happening to others as well. Why don't
we simply turn-off information messages?
Comment 4 Kevin McGuire CLA 2002-06-13 21:21:19 EDT
later
Comment 5 Jeff Brown CLA 2002-06-18 16:49:53 EDT
Is the connection still alive once the "get" finishes?  Perhaps the server is 
closing the connection on us (idle timeout or similar server policy).  Try 
sending a NOOP command after the RETR command completes and see if you get the 
221 there.  (So you'd see the bogus 221 after the next command initiated)

Certainly we handle the 221 just fine after a QUIT.  But receiving 221 as a 
result of a command other than QUIT _is_ a legitimate failure case (although 
not to spec) that should be reported because the operation that was just 
requested could not have completed.
Comment 6 Michael Valenta CLA 2005-05-06 16:16:36 EDT
This bug has not been touched in 2 years. Closing as WONTFIX. If you feel this 
bug is important, feel free to reopen it.