You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Tomasz (Jira)" <ji...@apache.org> on 2020/08/17 10:33:00 UTC
[jira] [Commented] (DIRMINA-1079) MINA fails to connect from behind
a proxy if endpoint is not resolved
[ https://issues.apache.org/jira/browse/DIRMINA-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17178899#comment-17178899 ]
Tomasz commented on DIRMINA-1079:
---------------------------------
[~elecharny] are you planing to release new version the patch? I am also impacted by the issue and needs to have it patched.
> 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
> 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-unsubscribe@mina.apache.org
For additional commands, e-mail: dev-help@mina.apache.org