Add support for dynamic HTTP client port configuration based on protocol/scheme [DATAGEODE-196] #240
Enables the user to configure the HTTP client port based on the protocol/scheme used (e.g. HTTP (80) vs. HTTPS (443)).
Enabling Cluster Configuration using HTTP is 1 example of SDG using a HTTP client to push configuration meta-data from client to server. The port cannot be required in all contexts, e.g. PCF when using PCC.
In some cases it might be better to let the networking infrastructure (e.g. Router) redirect the HTTP client as necessary
Backported to: 2.1.9 (Lovelace SR9)
The text was updated successfully, but these errors were encountered: