Add https support to elasticsearch_http #430
Closed
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
|
Struggling with HTTPS and HTTP Basic myself... Just to clear up some confusion on my part: is HTTPS supported at all by Logstash currently? I'd started to think it was from the combination of HTTPS and basic auth, but it appears as though it just doesn't like port 443. Here's the error I receive using HTTPS: Testing this fork now. Will respond with the results. EDIT: see this PR is one year old... I'm dumb. |
|
Loggly has https - not sure what's involved in getting it set up for elasticsearch or elasticsearch_river (considering elasticsearch_http is being deprecated) |
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.
Current pitfall is the cert must be signed through a trusted CA.