We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The elasticsearch-js client exposes Elasticsearch deprecations through the warnings getter:
warnings
https://github.com/elastic/elastic-transport-js/blob/main/src/Transport.ts#L333
However, this returns all the warning headers which could include warnings from intermediate proxies.
Given the htttp specification for warning headers https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.46
We should be able to include only warning headers from Elasticsearch with a pattern like /\d\d\d Elasticsearch-/
/\d\d\d Elasticsearch-/
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
The elasticsearch-js client exposes Elasticsearch deprecations through the
warnings
getter:https://github.com/elastic/elastic-transport-js/blob/main/src/Transport.ts#L333
However, this returns all the warning headers which could include warnings from intermediate proxies.
Given the htttp specification for warning headers https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.46
We should be able to include only warning headers from Elasticsearch with a pattern like
/\d\d\d Elasticsearch-/
The text was updated successfully, but these errors were encountered: