feat: Add support for the kbn-xsrf header #19
Conversation
This file contains hidden or 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
jphuynh
force-pushed
the
add-kbn-xsrf-header-support
branch
from
cac9ef1 to
08f5e82
Compare
jphuynh
changed the title
This should be ignored by ElasticSearch but is required when making Kibana API calls (https://www.elastic.co/guide/en/kibana/7.15/api.html#api-request-headers). Adding this will allow to both target ElasticSearch and Kibana API using aws-sigv4 signed requests. Similar to that PR that added the support to aws-es-proxy: abutaha/aws-es-proxy#72
jphuynh
force-pushed
the
add-kbn-xsrf-header-support
branch
from
08f5e82 to
122b272
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This should be ignored by ElasticSearch but is required when making Kibana API calls (https://www.elastic.co/guide/en/kibana/7.15/api.html#api-request-headers).
Adding this will allow to both target ElasticSearch and Kibana API using aws-sigv4 signed requests.
Similar to that PR that added the support to aws-es-proxy: abutaha/aws-es-proxy#72