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
Currently proxies are required to be InetSocketAddress, but netty allows any SocketAddress to be used as a proxy.
This can be seen in in the ProxyProvider class:
I'm interested in using UnixDomainSocket for proxies instead of InetSocketAddress.
Desired solution
Extend the functionality of the proxy provider class to allow passing a SocketAddress instead of a InetSocketAddress to a proxy.
I've made a rough example how that could be made in a fork of mine: AlexProgrammerDE@a76c01d
It tries to keep backwards support until the next major release is made.
I'd recommend the maintainers use my commit as a reference.
Considered alternatives
Support UnixDomainSocket instead, but it's probably easier to just support SocketAddress directly to allow other future implementations of that class.
The text was updated successfully, but these errors were encountered:
This commit adds new socketAddress methods and tries to keep backwards compat for users using the old address methods, which are deprecated. I'd recommend removing socketAddress and renaming it back to address on the next major release.
Fixesreactor#3242
…3243)
This commit adds new socketAddress methods and tries to keep backwards compat for users using the old address methods, which are deprecated. I'd recommend removing socketAddress and renaming it back to address on the next major release.
Fixes#3242
Currently proxies are required to be InetSocketAddress, but netty allows any SocketAddress to be used as a proxy.
This can be seen in in the ProxyProvider class:
reactor-netty/reactor-netty-core/src/main/java/reactor/netty/transport/ProxyProvider.java
Line 429 in ed7c964
Motivation
I'm interested in using UnixDomainSocket for proxies instead of InetSocketAddress.
Desired solution
Extend the functionality of the proxy provider class to allow passing a SocketAddress instead of a InetSocketAddress to a proxy.
I've made a rough example how that could be made in a fork of mine: AlexProgrammerDE@a76c01d
It tries to keep backwards support until the next major release is made.
I'd recommend the maintainers use my commit as a reference.
Considered alternatives
Support UnixDomainSocket instead, but it's probably easier to just support SocketAddress directly to allow other future implementations of that class.
The text was updated successfully, but these errors were encountered: