Fix bug for URI creation when Port not given #125
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
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.
No additional logif when user/pass given but port not given, resulting in extra colon in the URI to elastic and breaking functionality.
Also, since the bitnami stack for ELK has elasticsearch exposed via /elasticsearch on the 80 port, adding port 80 results in /elasticsearch:80 instead of :80/elasticsearch, breaking all of the endpoints. As bitnami is set to port 80 on default, adding this fix also neatly fixes the issue for anyone trying to use default bitnami settings.