-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for tcp binding to route by port numbers #299
Conversation
…r to handle port values in JSON, and add tests for reading and writing with port values and port ranges
…cal address in the resolution process.
@@ -281,6 +281,7 @@ public NamespaceConfig parse( | |||
catch (Throwable ex) | |||
{ | |||
logError(ex.getMessage()); | |||
ex.printStackTrace(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please remove this logging.
InetSocketAddress remote) | ||
{ | ||
return routes.stream() | ||
.filter(r -> r.matches(remote.getAddress())) | ||
.filter(r -> r.matches(local)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like we only need one address
parameter here, not both local
and remote
.
Then in TcpServerFactory
, we'd need to pass local
socket address to match the local port we are listening on, and in TcpClientFactory
, we'd need to pass remote
socket address to match the remote port we are connecting to, agree?
@@ -84,7 +84,7 @@ public class TcpServerFactory implements TcpStreamFactory | |||
|
|||
private final ProxyBeginExFW.Builder beginExRW = new ProxyBeginExFW.Builder(); | |||
|
|||
private final EngineContext context; | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please remove the extra blank line.
@@ -280,7 +280,7 @@ public NamespaceConfig parse( | |||
} | |||
catch (Throwable ex) | |||
{ | |||
logError(ex.getMessage()); | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apologies, please restore this line.
Description
Support for tcp binding to route by port numbers
Fixes #294