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, Proxyman only performs SSL handshakes with remote servers if the remote port is 443.
I would like to request a new configuration option in the Reverse Proxy configuration window to allow specifying whether the target port is SSL/TLS or not.
Why this feature/change is important?
In a development environments, there are often multiple TLS services run on different ports of the same target host. Also some environments use TLS on non-standard ports (not 443), which cannot be reconfigured.
This limitation makes it challenging to utilize Proxyman's reverse proxy in such environments. Adding this configuration option would greatly enhance flexibility and usability for developers working with diverse configurations.
The text was updated successfully, but these errors were encountered:
@NghiaTranUIT, I just checked out the beta build and the new SSL checkbox is working great!
The only thing I noticed is a small cosmetic issue with the label (1). It still says that HTTPS is only negotiated on port 443.
Description
Currently, Proxyman only performs SSL handshakes with remote servers if the remote port is 443.
I would like to request a new configuration option in the Reverse Proxy configuration window to allow specifying whether the target port is SSL/TLS or not.
Why this feature/change is important?
In a development environments, there are often multiple TLS services run on different ports of the same target host. Also some environments use TLS on non-standard ports (not 443), which cannot be reconfigured.
This limitation makes it challenging to utilize Proxyman's reverse proxy in such environments. Adding this configuration option would greatly enhance flexibility and usability for developers working with diverse configurations.
The text was updated successfully, but these errors were encountered: