fix: add globalheader to client#getNodesInfo() #24
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.
i use go-elasticsearch to visit elasticsearch servers, and due to the restrictions of my company, i have to add a custom header to the request. go-elasticsearch config and underlying transport client config provides a global header field to do this thing, like the bode below
it works when i just perform a search, because the underlying transport client set the global header before performing a request like this
c.setReqGlobalHeader(req)
is used to set the global header.but when it comes to discoverNodes(), the global header is not set, leading to discoverNodes failure in my case
I think this is a mistake, and this pr add
c.setReqGlobalHeader(req)
togetNodesInfo()
to set global header