[NET-291] enterLocalPassiveMode is set back to Active on connect

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 2.0
• Fix Version/s: 3.1
• Component/s: FTP
• Assignee: Unassigned
• Reporter: Kevin Brown
• Created: 19/Aug/09 19:52
• Updated: 29/Feb/12 20:35
• Resolved: 10/Jan/12 19:39

Description

enterLocalPassiveMode (exhibit A) docs claim that mode will be set to PASSIVE_LOCAL_DATA_CONNECTION_MODE "some other method such as" enterLocalActiveMode is called (exhibit B). However, active mode is being entered after connect is called. This behavior can be easily observed by modifying FtpExample by moving ftp.enterLocalPassiveMode() to before ftp.connect(server).

Perhaps either the code or docs could be updated to remedy this. Versions prior to 2.0 behaved as documented.

exhibit A:
/***

• Set the current data connection mode to
• <code> PASSIVE_LOCAL_DATA_CONNECTION_MODE </code>. Use this
• method only for data transfers between the client and server.
• This method causes a PASV command to be issued to the server
• before the opening of every data connection, telling the server to
• open a data port to which the client will connect to conduct
• data transfers. The FTPClient will stay in
• <code> PASSIVE_LOCAL_DATA_CONNECTION_MODE </code> until the
• mode is changed by calling some other method such as
• {@link #enterLocalActiveMode enterLocalActiveMode() }

  ***/
  public void enterLocalPassiveMode()

  { __dataConnectionMode = PASSIVE_LOCAL_DATA_CONNECTION_MODE; // These will be set when just before a data connection is opened // in _openDataConnection_() __passiveHost = null; __passivePort = -1; }

exhibit B

@Override
protected void connectAction() throws IOException

{ super._connectAction_(); __initDefaults(); }