You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Anton Novikov (JIRA)" <ji...@apache.org> on 2018/03/02 15:29:00 UTC
[jira] [Created] (DIRMINA-1079) MINA fails to connect from behind a
proxy if endpoint is not resolved
Anton Novikov created DIRMINA-1079:
--------------------------------------
Summary: 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
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. A somewhat similar problem exists with SOCKS 4a, where a similar check does not exist, see ProtocolFactory line 198
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)