Problems with TLS enabled HTTP Proxy for Proxy Tunnel entries

Problems with TLS enabled HTTP Proxy for Proxy Tunnel entries

avatar

Hi. I tried protecting my HTTP proxy with TLS in order not to send Baisc Auth data over plaintext between client (RDM) and the proxy server.
In RDM I use entries of Type "Proxy Tunnel (HTTP, SOCKS4, SOCKS4A, SOCKS5).
When setting Usage to Port Forward, there is a field named Proxy Type which I can set to HTTPS. It does not work as expected.
When setting to HTTP it tries plaintext connection against the proxy server which fails obviously.

I tried entering https://xxxx as Host (worked for web session entries in proxy tab), but with no luck - it seems to try to resolve the whole field as an hostname.

Is it currently supported in RDM to connect to a typical http (connect) proxy over TLS? If not, when will it be?

Because this type of proxies currently ONLY support Basic Auth, it is really not usable. At least adding Kerberos/Negotiate support would allow to skip the TLS layer, but in my opinion TLS layer should be supported regardless authentication protocol used.

Best Regards,
Bart

All Comments (2)

avatar

Hello,

we are going to have to run some tests.
To start with, I would like to clarify so we can answer you better, are you using RDM on Windows or on Mac?
Because we don't have added the Usage field yet on MacOs.

Best regards,

Michel Lambert

avatar

I am using currently RDM on Windows (version 2025.1.25.0 64-bit) but plan also to use it with the version for Mac in near future.