Hostname protocol fix #8
Open
Conversation
This file contains hidden or 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
…otocol to be set within the config. e.g example.contrastsecurity.com or https://example.contrastsecurity.com
JoeBeeContrast
requested review from
ChrisEdwards,
JacobMagesHaskinsContrast,
dougj-contrast and
jason-at-contrast
jason-at-contrast
approved these changes
Aug 8, 2025
JacobMagesHaskinsContrast
approved these changes
Aug 8, 2025
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 fix allows the user to specify the TS server as either
example.contrastecurity.com or https://example.contrastsecurity.com
If the protocol is set in the config, that is used. If not it defaults to what is in the application.properties. And if not there for some reason defaults to https.