Return-Path: X-Original-To: apmail-directory-dev-archive@www.apache.org Delivered-To: apmail-directory-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 55F99D5CD for ; Tue, 13 Nov 2012 11:12:13 +0000 (UTC) Received: (qmail 9870 invoked by uid 500); 13 Nov 2012 11:12:13 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 9765 invoked by uid 500); 13 Nov 2012 11:12:13 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 9726 invoked by uid 99); 13 Nov 2012 11:12:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Nov 2012 11:12:12 +0000 Date: Tue, 13 Nov 2012 11:12:12 +0000 (UTC) From: "Pierre-Arnaud Marcelot (JIRA)" To: dev@directory.apache.org Message-ID: <1127321130.106882.1352805132358.JavaMail.jiratomcat@arcas> In-Reply-To: <963003195.106759.1352803692018.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (DIRSTUDIO-846) Socks proxy does not work with version 2.0.0-M3, connections still go directly to server without using the socks server defined MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DIRSTUDIO-846?page=3Dcom.atlass= ian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1= 3496112#comment-13496112 ]=20 Pierre-Arnaud Marcelot commented on DIRSTUDIO-846: -------------------------------------------------- OK, so connections using JNDI respect the Socks proxy settings and those us= ing the Apache Directory LDAP Client API don't, is that it? If that's the case, this is *not* a normal behavior and we probably need to= tell the JVM to use the Socks proxy settings even with the Apache Director= y LDAP Client API. I will look into it. =20 > Socks proxy does not work with version 2.0.0-M3, connections still go dir= ectly to server without using the socks server defined > -------------------------------------------------------------------------= ------------------------------------------------------ > > Key: DIRSTUDIO-846 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-846 > Project: Directory Studio > Issue Type: Bug > Affects Versions: 2.0.0-M3 > Environment: Tested on Ubuntu 12.10 32bits and Redhat Enterprise = 6.0 64 Bits. > Reporter: Gr=C3=A9goire BELLON-GERVAIS > Priority: Critical > Fix For: 1.5.3 > > > This behaviour has been tested on an Ubuntu 12.10 32bits and a Redhat Ent= erprise 6.0 64 Bits. > Same error on both. > Under version 1.5.3, when we set proxy server to socks and put "Active Pr= ovider" to Manual, connections go through the defined socks. > Under version 2.0.0-M3, when we set also proxy server to socks and put "A= ctive Provider" to Manual, the behaviour is different : > - One connection go directly to the server and not through the socks serv= er, > - another connection go through the socks server. > Checked with netstat to see the connections informations. > And of course, we can't connect to ldap server. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs For more information on JIRA, see: http://www.atlassian.com/software/jira