mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Valliere (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DIRMINA-1079) MINA fails to connect from behind a proxy if endpoint is not resolved
Date Sat, 03 Mar 2018 17:25:00 GMT

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

Jonathan Valliere commented on DIRMINA-1079:
--------------------------------------------

Need a bit more information.  

Your setup looks like this MINA -> PROXY -> INTERNET?
Are you asserting that MINA should be able to function without being able to resolve the Address
in this situation?

> 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
>            Priority: Major
>
> 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
(v7.6.3#76005)

Mime
View raw message