-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Console should not function as an open web proxy #7059
Comments
To clarify, the requests should be sent to whichever ES that kibana is configured to use rather than hardcoding localhost:9200. |
Thanks @epixa. That makes more sense :) |
ycombinator
added a commit
to ycombinator/kibana
that referenced
this issue
May 6, 2016
ycombinator
added a commit
to ycombinator/kibana
that referenced
this issue
May 10, 2016
ycombinator
added a commit
that referenced
this issue
May 11, 2016
Disallow Console from functioning as an open web proxy
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, its possible to use Console as an open web proxy because users can enter any base URL in the input box up top. Evidence (thanks @rashidkpc):
For now, the consensus is to remove the input box on the client-side and, on the server-side, only send requests to
http://localhost:9200
. In the future, we might allow user to configure a list of Elasticsearch base URLs that they can then select from on the client-side.The text was updated successfully, but these errors were encountered: