-
Notifications
You must be signed in to change notification settings - Fork 79
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
Expand allowed CORS headers for cross-origin Ajax requests #40
Comments
Hi @mkfmnn, I'm not really familiar with CORS, can you suggest what headers need to be added/removed in order to allow it to work with Kibana? |
The same changes made in the linked elasticsearch commit:
in addition to the existing
|
This would be super awesome to have. |
Just ran into this issue trying to use Kibana 3, would be great to get this fixed. |
I've made what I think is the required two-line change however I'm unsure how to build a "thing" be it a zip, jar, whatever. If I run "mvn package" it starts the test suite and the first stacktrace I get is this:
Any ideas? |
I don't think my changes have broken the test suite as it fails in pretty much the same way if I revert my changes. I'm not a Maven wizard but using "mvn package -DskipTests" gives me a zip archive I can copy onto my ES server and it looks like it's working, Kibana 3 seems to work. |
Hey guys, I tried to pull request of the updated code, but no news until now!! For now I added the CORS support, as suggested by mkfmnn and upgraded the plugin for versions 0.90.10 and 1.0.0. If you need any help, or want something added to the plugin, just let me know!! Abs |
Bueller? Any chance we can get this merged? It's a two line fix which means everyone can use this plugin with Kibana. This project is clearly maintained as it's been updated recenty to work with ES 1.x but you'd never guess that looking at the issues queue. |
+1 |
The suggested fix is not enough. I use Basic authentication for my cluster, and I would need these headers to allow browsers to hit it:
https://developer.mozilla.org/en-US/docs/HTTP/Access_control_CORS#Requests_with_credentials |
This is how I managed to make CORS work with Firefox, Safari and IE. As @thejohnfreeman said, one needs to send
Maybe it is enough to send these headers for For Safari, you also need to make sure that you return a
I can send a pull request for these if you want. |
@hiredman: this is unfortunately not enough, you really need to send back the |
Hi, I've tested a basic authenticated set up with nginx instead of Jetty and setting the following in my elasticsearch.yml file satisified CORS:
Could the elasticsearch-jetty be extended to support the |
Any feedback on this issue? If I cant use elasticsearch-jetty with Kibana, then it looks like I'll need to abandon jetty and look for another basic auth solution 👎 |
elasticsearch-jetty doesn't work with Kibana 3 because it sends an insufficiently broad set of Access-Control-Allow-* headers.
See this commit in elasticsearch core: elastic/elasticsearch@f659cad
The text was updated successfully, but these errors were encountered: