| [tm-dev] FTP passive mode |
|
Hi TM Committers, With adopting Commons Net 3.2 for FTP, and since I thus had to test FTP anyways, I’ve also finally enabled FTP Passive Mode by default: https://bugs.eclipse.org/bugs/show_bug.cgi?id=269442#c7 This is a very relevant change, which should go into the New & Noteworthy. To give you some background : Passive Mode means, that any connection to the FTP server is made from the client.
The active mode, by contrast, means that while the control connection is initiated by the client, the server “calls back” actively to transfer the data. This obviously can’t work when the client is behind a firewall or NAT router. Therefore
passive mode is being recommended for most FTP clients as the default. In TM/RSE it’s very hard to find how to switch from active mode to passive mode, therefore the choice of default transfer mode is very relevant. I cannot rule out the possibility of problems or regressions with passive mode, and in fact
I did already find one problem with a local server under very high load:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=408223 But after all the testing I’ve done, I still think that going for passive mode is the right direction and the Kepler 3.5.0 release is the right time for such a change. I can back out the change easily if you disagree, but I do hope that you support this direction and that you help testing the change. Let me know what you think – easiest by voting “review+” on the bug and/or commenting on it: https://bugs.eclipse.org/bugs/show_bug.cgi?id=269442 You can get the “passive mode default” from TM Hudson-master-nightly #896 or later: https://hudson.eclipse.org/hudson/job/tm-master-nightly/ Thanks, Martin -- Martin Oberhuber, SMTS / Product Architect – Development Tools,
Wind River direct +43.662.457915.85 fax +43.662.457915.6 |