You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Stephan Hradek (JIRA)" <ji...@apache.org> on 2013/06/04 10:52:20 UTC

[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

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

Stephan Hradek commented on DIRSTUDIO-846:
------------------------------------------

See DIRSTUDIO-920: With the release I downloaded today (2.0.0.v20130517) connection go through the SOCKS Proxy.

But unfortunately ALL seem to go through the proxy, no matter which hosts you define in "Proxy bypass".
                
> Socks proxy does not work with version 2.0.0-M3, connections still go directly 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égoire BELLON-GERVAIS
>            Priority: Critical
>             Fix For: 1.5.3
>
>
> This behaviour has been tested on an Ubuntu 12.10 32bits and a Redhat Enterprise 6.0 64 Bits.
> Same error on both.
> Under version 1.5.3, when we set proxy server to socks and put "Active Provider" to Manual, connections go through the defined socks.
> Under version 2.0.0-M3, when we set also proxy server to socks and put "Active Provider" to Manual, the behaviour is different :
> - One connection go directly to the server and not through the socks server,
> - 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 administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira