Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for response warning header #762

Closed
jbudz opened this issue Jan 30, 2019 · 2 comments
Closed

Support for response warning header #762

jbudz opened this issue Jan 30, 2019 · 2 comments

Comments

@jbudz
Copy link
Member

jbudz commented Jan 30, 2019

Elasticsearch includes deprecations in a response warning header, elastic/elasticsearch#17804. Including these in the response or log methods may be useful for staying up to date.

@delvedor
Copy link
Member

delvedor commented Jan 30, 2019

Hello!
You can access the headers when using the callback style, the function should have the following signature: err, body, status, headers.

Currently, I'm working on a complete rewrite of the client, that you can find in the next branch. In the next client, the returned value will be an object with the following keys { body, headers, statusCode, warnings } for both promises and callbacks.

@jbudz
Copy link
Member Author

jbudz commented Jan 30, 2019

Awesome, thanks for the info @delvedor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants