You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a use case where we have a bridge behind a TCP proxy. This is useful as a method to share port 443 with multiple services on the server. The issue with this approach is that ice4J doesn't see the correct remote address.
While not strictly a problem, it would be great if ice4J could support the proxy protocol on TCP connections. This would, at the very least, allow logs to show the correct remote host addresses.
The text was updated successfully, but these errors were encountered:
We have a use case where we have a bridge behind a TCP proxy. This is useful as a method to share port 443 with multiple services on the server. The issue with this approach is that ice4J doesn't see the correct remote address.
While not strictly a problem, it would be great if ice4J could support the proxy protocol on TCP connections. This would, at the very least, allow logs to show the correct remote host addresses.
The text was updated successfully, but these errors were encountered: