Use gateway client attls status in eureka object to determine http vs… #583
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… https Signed-off-by: 1000TurquoisePogs <sgrady@rocketsoftware.com>
Signed-off-by: 1000TurquoisePogs <sgrady@rocketsoftware.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR builds upon #580 by altering the eureka object's status of https/http true/false dependent upon the status of the gateway's client attls setting.
This is because, client attls alters whether you must send a request as 'http' or 'https' in order to avoid double-tls, or no-tls situations.
In this PR, the app-server reports itself as 'http' if the gateway has client tls enabled, so that when the gateway contacts the app-server, it will HTTPS, as desired.
This logic does not consider the state of the app-server's server ATTLS setting, because whether server ATTLS is enabled or disabled, the app-server should always be HTTPS.