[
https://issues.apache.org/jira/browse/NET-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved NET-468.
----------------------
Resolution: Fixed
> Request for native support for socks proxy routing with Commons net FTP
> -----------------------------------------------------------------------
>
> Key: NET-468
> URL: https://issues.apache.org/jira/browse/NET-468
> Project: Commons Net
> Issue Type: Improvement
> Components: FTP
> Affects Versions: 1.4, 2.0, 3.0.1, 3.1, 3.4
> Environment: We use commons net in out products for all
> communication to an FTP server. OS : All. No other environment specifications.
> Reporter: Ramya Rajendiran
> Attachments: imapproxy.java, sockclient-proxy3.diff,
> sockclient-proxy4.diff, sockclient-proxy5.diff, sockclient-proxy6.diff,
> sockclient-proxy7.diff
>
>
> Commons net currently does not natively support connection to an FTP server
> via a socks proxy. The only way of achieving this would be to work at the
> socket level as observed here
> http://wiki.apache.org/commons/Net/FrequentlyAskedQuestions. (by setting JVM
> properties socksProxyPort and socksProxyPortHost)
> However, a major side effect of this all connections on this JVM will go
> through the socks proxy since this setting is at the JVM level. This is
> sometimes undesirable as the business requirements are such that only certain
> applications on the JVM need to go through the socks proxy. There are no
> existing workarounds to conditionally prevent other applications to not be
> routed through the socks proxy. This makes our application which consumes the
> commons net unusable for such businesses.
> Providing native support for socks proxy with commons net for FTP, will go a
> long way in supporting such common scenarios and business continuity.
> Therefore raising this enhancement request.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
