[MISC] Fix malformed transport.request paths #6843
Merged
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.
While testing with Charles proxy I realized that when using the ES client's Transport object to make a request the
path
parameter should have a leading/
. The URLs being generated looked likelocalhost:9200_ingest/pipeline/kibana-foo
. Strangely, this didn't cause any issues for elasticsearch, but it prevented the use of Charles and might cause subtle errors down the road, so I went ahead and fixed the paths.