Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for dynamic HTTP client port configuration based on protocol/scheme [DATAGEODE-196] #240

Closed
spring-projects-issues opened this issue May 20, 2019 · 0 comments

Comments

@spring-projects-issues
Copy link

@spring-projects-issues spring-projects-issues commented May 20, 2019

John Blum opened DATAGEODE-196 and commented

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


Referenced from: commits 1b4eec3, aba1781

Backported to: 2.1.9 (Lovelace SR9)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.