[jira] [Updated] (NET-468) Request for native support for socks proxy routing with Commons net FTP
[ https://issues.apache.org/jira/browse/NET-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated NET-468: - Fix Version/s: (was: 3.2) > 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: 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.3.4#6332)
[jira] [Updated] (NET-468) Request for native support for socks proxy routing with Commons net FTP
[ https://issues.apache.org/jira/browse/NET-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated NET-468: - Affects Version/s: 3.4 > 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: 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.3.4#6332)
[jira] [Updated] (NET-468) Request for native support for socks proxy routing with Commons net FTP
[ https://issues.apache.org/jira/browse/NET-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated NET-468: - Fix Version/s: 3.2 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 Fix For: 3.2 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 For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NET-468) Request for native support for socks proxy routing with Commons net FTP
[ https://issues.apache.org/jira/browse/NET-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated NET-468: Attachment: sockclient-proxy6.diff New version of the patch: - Fix misspelled words. - Add testing for side effects to the new test org.apache.commons.net.SocketClientTest - Add missing @since tags - Fix formatting of if statements - Other small improvements 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 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
[jira] [Updated] (NET-468) Request for native support for socks proxy routing with Commons net FTP
[ https://issues.apache.org/jira/browse/NET-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bogdan Drozdowski updated NET-468: -- Attachment: sockclient-proxy4.diff OK, the last version. This time created with the svn diff command. If you wish to receive only such patches, write that on the http://commons.apache.org/net/code-standards.html page. If you don't want to receive patches, simply disable this functionality or make this JIRA private. If you don't like this patch, simply say rejected and don't bother explaining. I also have other things to do in my spare time. 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 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
[jira] [Updated] (NET-468) Request for native support for socks proxy routing with Commons net FTP
[ https://issues.apache.org/jira/browse/NET-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bogdan Drozdowski updated NET-468: -- Attachment: (was: sockclient-proxy2.diff) 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
[jira] [Updated] (NET-468) Request for native support for socks proxy routing with Commons net FTP
[
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
[jira] [Updated] (NET-468) Request for native support for socks proxy routing with Commons net FTP
[ https://issues.apache.org/jira/browse/NET-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bogdan Drozdowski updated NET-468: -- Attachment: sockclient-proxy2.diff OK, here you go. Sockets have no getter methods for proxies and I don't want a test case to depend on something external (like a proxy server running on some host+port), so this simple test case focuses on checking if set+get actually work. Test is passed. 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-proxy2.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
[jira] [Updated] (NET-468) Request for native support for socks proxy routing with Commons net FTP
[ https://issues.apache.org/jira/browse/NET-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bogdan Drozdowski updated NET-468: -- Attachment: (was: sockclient-proxy.diff) 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-proxy2.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
[jira] [Updated] (NET-468) Request for native support for socks proxy routing with Commons net FTP
[ https://issues.apache.org/jira/browse/NET-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bogdan Drozdowski updated NET-468: -- Attachment: sockclient-proxy.diff Native proxy support is already present - you can install your own SocketFactory which creates Sockets with Proxy support. The attached file, sockclient-proxy.diff, makes this easier - when you set a Proxy, it creates and installs a new DefaultSocketFactory, which now has easy Proxy support (also thanks to this patch). Call setSocketFactory() for now, until this patch is included in the distribution (if it will be). 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-proxy.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
[jira] [Updated] (NET-468) Request for native support for socks proxy routing with Commons net FTP
[ https://issues.apache.org/jira/browse/NET-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated NET-468: - Priority: Major (was: Critical) 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 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
