[ https://issues.apache.org/jira/browse/DIRMINA-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17066477#comment-17066477 ]
Rishabh Agarwal commented on DIRMINA-1079: ------------------------------------------ Version 2.0.23 is not available to use. Are you planning to make version 2.0.23 available later or will fix this in next 2.0.x / 2.1.0 release? Please let me know as I am also affected by this issue. > MINA fails to connect from behind a proxy if endpoint is not resolved > --------------------------------------------------------------------- > > Key: DIRMINA-1079 > URL: https://issues.apache.org/jira/browse/DIRMINA-1079 > Project: MINA > Issue Type: Bug > Components: Handler > Affects Versions: 2.0.16 > Reporter: Anton Novikov > Assignee: Jonathan Valliere > Priority: Major > Fix For: 2.0.23 > > Attachments: DIRMINA-1079.patch > > > MINA fails to connect from behind a proxy if endpoint address is not > resolved. This happens for both HTTP and SOCKS proxy and it seems that the > reason for this are typos in HttpProxyRequest and SocksProxyRequest. The > following changes seem to fix the issue: > HttpProxyRequest line 105: replace {{if (!endpointAddress.isUnresolved()) {}} > with {{if (endpointAddress.isUnresolved()) {}} > SocksProxyRequest line 162: replace {{if (adr != null && !adr.isUnresolved()) > {}} with {{if (adr != null && adr.isUnresolved()) {}} > Note the negation is gone in both cases -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org For additional commands, e-mail: dev-h...@mina.apache.org