-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
The ProxyHandler created by the reverse-proxy() builder does not provide a default SSL context. Therefore, it cannot be used by any SSL backend, severely limiting its usefulness.
[DEBUG] io.undertow.request: Failed to connect java.io.IOException: UT000065: SSL must be specified to connect to a https URL at io.undertow.client.http.HttpClientProvider.connect(HttpClientProvider.java:94) at io.undertow.client.UndertowClient.connect(UndertowClient.java:161) at io.undertow.server.handlers.proxy.ProxyConnectionPool.openConnection(ProxyConnectionPool.java:274) at io.undertow.server.handlers.proxy.ProxyConnectionPool.connect(ProxyConnectionPool.java:550) at io.undertow.server.handlers.proxy.LoadBalancingProxyClient.getConnection(LoadBalancingProxyClient.java:340) at io.undertow.server.handlers.proxy.ProxyHandler$ProxyClientHandler.run(ProxyHandler.java:329)
Granting that there are some specific edge cases that would not work, the default behavior of the reverse proxy builder should be to detect an HTTPS URL and provide a default SSL context so the proxy can be used to connect to a remove endpoint over HTTPS.
