Return-Path: X-Original-To: apmail-commons-issues-archive@minotaur.apache.org Delivered-To: apmail-commons-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C3A2BDC35 for ; Wed, 4 Jul 2012 11:21:39 +0000 (UTC) Received: (qmail 94573 invoked by uid 500); 4 Jul 2012 11:21:38 -0000 Delivered-To: apmail-commons-issues-archive@commons.apache.org Received: (qmail 94320 invoked by uid 500); 4 Jul 2012 11:21:38 -0000 Mailing-List: contact issues-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: issues@commons.apache.org Delivered-To: mailing list issues@commons.apache.org Received: (qmail 94183 invoked by uid 99); 4 Jul 2012 11:21:35 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jul 2012 11:21:35 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 1941F142822 for ; Wed, 4 Jul 2012 11:21:35 +0000 (UTC) Date: Wed, 4 Jul 2012 11:21:35 +0000 (UTC) From: "Gary D. Gregory (JIRA)" To: issues@commons.apache.org Message-ID: <1060212360.2899.1341400895105.JavaMail.jiratomcat@issues-vm> In-Reply-To: <1862268854.14889.1338359723524.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (NET-468) Request for native support for socks proxy routing with Commons net FTP MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/NET-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13406450#comment-13406450 ] Gary D. Gregory commented on NET-468: ------------------------------------- Hello, I cannot apply the patch. Did you use SVN diff to create the patch? The format looks odd: I see: {noformat} --- src/main/java/org/apache/commons/net/SocketClient.java 2012-04-24 17:30:45.596176007 +0200 +++ ../../org/apache/commons/net/SocketClient.java 2012-07-02 18:21:00.287784277 +0200 ... {noformat} and expect: {noformat} Index: src/main/java/org/apache/commons/net/SocketClient.java =================================================================== --- src/main/java/org/apache/commons/net/SocketClient.java (revision 1357226) +++ src/main/java/org/apache/commons/net/SocketClient.java (working copy) ... {noformat} Thank you, Gary > 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