[ 
https://issues.apache.org/jira/browse/NET-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bogdan Drozdowski updated NET-468:
----------------------------------

    Attachment: sockclient-proxy3.diff

No, I didn't use the SVN diff command to create the patch. I prefer to keep my 
working copy clean, so I copy the files I wish to modify somewhere else and 
perform a "diff -buraN" command. To apply the patch, use the "patch" utility, 
common in many Linux distributions. The command will be something similar to
{code}patch -F20 -p0 < /path/to/sockclient-proxy2.diff{code}
(run in the directory that contains the "src" directory). If that's a problem, 
I can use "svn diff".
The previous patch had an error - the test wasn't in src/test. Use the third 
version I've just attached.
                
> 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
>
>
> 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

        

Reply via email to