commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bogdan Drozdowski (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NET-468) Request for native support for socks proxy routing with Commons net FTP
Date Sat, 14 Jul 2012 11:31:35 GMT

    [ https://issues.apache.org/jira/browse/NET-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414348#comment-13414348
] 

Bogdan Drozdowski commented on NET-468:
---------------------------------------

Yes, it would be faster to run the test this way, it wouldn't use any bandwidth or resources
of existing servers and it wouldn't fail if the external servers become inaccessible for maintenance
periods. The same could be implemented for other protocols. The would probably do for simple
tests.
The problem with this approach is that we would be testing our software not only with another
piece of our software, but also with not-so-real-life software. The authors of the embedded
server could implement something in a specific way that could, for example, work if we implement
FTPClient the same way but would make FTPClient fail when connecting to real servers (or vice-versa:
connecting to real servers would work, but tests would fail). This could be especially the
case with the Socks protocol (like I wrote before, not all Socks servers seem to work with
Java).
Another approach would be seeting up some test servers (using commonly-used software, like
ProFTPd or vsftpd for FTP) so that no resources outside apache.org would be needed.
                
> 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
>         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: 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message