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

Allow forwarding of proxy/request headers to ES #364

Merged
merged 1 commit into from
May 21, 2019

Conversation

psk-ixolit
Copy link
Contributor

This is an implementation for #349 and #295.

It extends the host configuration with a forward_headers field.
It specifies which headers of the original request towards cerebro should be forwarded to the ES instance.

@moliware
Copy link
Collaborator

Hi! Thanks for the contribution. I'll have a deeper look before merging it.

@moliware moliware merged commit 4342348 into lmenezes:master May 21, 2019
@moliware
Copy link
Collaborator

Hi @psk-ixolit, I remamed the property to headers-whitelist so that it's similar to kibana's naming (they have a similar setting called: elasticsearch.requestHeadersWhitelist).

Thank you very much for contributing, I'll ty to release a new version by the end of this week. As I don't use search guard, would be much appreciated if you could test it and give us feedback. Thanks!

@arturmartins
Copy link

@moliware: any chance to get a new release/version soon?

@kiblik
Copy link

kiblik commented Feb 21, 2020

This parameter looks pretty nice but it doesn't work for me.

I tried to set the same headers which work for kibana (requestHeadersWhitelist) but ES returns HTTP 401.

When I tried to inspect traffic (tcpdump 'tcp port 9200 or tcp port 9000') I saw that Cerebro doesn't pass my headers to requests.

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

Successfully merging this pull request may close these issues.

4 participants