elasticsearch.js 客户端连接被拒绝：Access-Control-Allow-Origin 无法识别？

我一直在尝试使用elasticsearch.jquery.min.js ping 本地运行的elasticsearch，每次都会收到“无活动连接”错误。

ETA：在 Chrome 中，我看到看起来相当低级别的“连接被拒绝”。我正在 MacOS X 上进行开发，我的浏览器通过以下方式指向该页面http://localhost/~myuserid/SiteName/。当我访问时localhost:9200这显然属于跨域 CORS 要求。

我在 Chrome 控制台中看到以下错误：

XMLHttpRequest cannot load http://localhost:9200/?hello=elasticsearch!.
No 'Access-Control-Allow-Origin' header is present on the requested resource.
Origin 'http://localhost' is therefore not allowed access.

Per http://enable-cors.org/server_apache.html http://enable-cors.org/server_apache.html我已将以下内容添加到 /etc/apache2/httpd.conf 中：

<Directory />
    Header set Access-Control-Allow-Origin "localhost:9200"
    AllowOverride none
    Require all denied
</Directory>

and run

$ sudo apachectl -t
$ sudo apachectl -k graceful

但错误仍然存​​在。还有其他我忽略的设置吗？

我是 elasticsearch.js 的菜鸟。我需要在elasticsearch方面做些什么来允许来自浏览器的客户端连接，或者其他什么？

我正在跟进the book https://www.elastic.co/guide/en/elasticsearch/client/javascript-api/current/quick-start.html在我的 ping 尝试中：

var client = new $.es.Client({
  hosts: 'localhost:9200'
  });

client.ping(
  {
    requestTimeout: Infinity,
    // undocumented params are appended to the query string
    hello: "elasticsearch!"
    },
  function (error) {
    if (error) {
      console.error('elasticsearch cluster is down!');
      console.error(error);
    } else {
      console.log('All is well');
      }
    }
  );

但我收到以下错误：

"WARNING: 2015-10-10T07:00:16Z"        elasticsearch.jquery.min.js:14:10575
  Unable to revive connection: http://localhost:9200/

"WARNING: 2015-10-10T07:00:16Z"        elasticsearch.jquery.min.js:14:10575
  No living connections

我可以在命令行上使用curl 进行连接，拉取和插入数据等：

$ curl "localhost:9200/_cat/indices?v"
health status index             pri rep docs.count docs.deleted store.size pri.store.size 

green  open   fuddle              1   0          3            0     12.9kb         12.9kb                                                
green  open   faddle              1   0          0            0       144b           144b 

ETA 附加诊断。 Google Chrome 显示失败尝试的以下网络跟踪。在 HTTP 层，响应看起来像是正在发生。

General
  Remote Address:[::1]:9200
  Request URL:http://localhost:9200/?hello=elasticsearch!
  Request Method:HEAD
  Status Code:200 OK
Response Headers
  Content-Length:0
  Content-Type:text/plain; charset=UTF-8
Request Headers
  Accept:text/plain, */*; q=0.01
  Accept-Encoding:gzip, deflate, sdch
  Accept-Language:en-US,en;q=0.8
  Connection:keep-alive
  Content-Length:0
  Host:localhost:9200
  Origin:http://localhost
  Referer:http://localhost/~browsc3/Opticon/
  User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.101 Safari/537.36
Query String Parameters
  view URL encoded
  hello:elasticsearch!

wget 中的相同请求：

wget http://localhost:9200/?hello=elasticsearch!
--2015-10-10 09:47:13--  http://localhost:9200/?hello=elasticsearch!
Resolving localhost... ::1, 127.0.0.1
Connecting to localhost|::1|:9200... connected.
HTTP request sent, awaiting response... 200 OK
Length: 342 [application/json]
Saving to: 'index.html?hello=elasticsearch!'

index.html?hello=elastics 100%[=====================================>]     342  --.-KB/s   in 0s     

2015-10-10 09:47:13 (65.2 MB/s) - 'index.html?hello=elasticsearch!' saved [342/342]

我真的不知道从这里该去哪里。我在 googlz 上看到很多对该错误的引用，但没有一个情况看起来完全相似。感觉就像我遇到了一些配置错误，但我找不到任何可以表明那是什么的东西。

嗯，那是一件艰难的事。

这是修复它的方法：

Per http://enable-cors.org/server_apache.html http://enable-cors.org/server_apache.html, in /etc/apache2/httpd.conf，配置Access-Control-Allow-Origin：

<Directory />
    # Add the following line to enable CORS to connect to local elasticsearch.
    Header set Access-Control-Allow-Origin "localhost:9200"
    AllowOverride none
    Require all denied
</Directory>

Per https://jsbroadcast.com/elastic-search-cors/ https://jsbroadcast.com/elastic-search-cors/, in elasticsearch-1.7.0/config/elasticsearch.yml add:

http.cors.enabled : true // 
http.cors.allow-origin: "/.*/"
http.cors.allow-methods : OPTIONS, HEAD, GET, POST, PUT, DELETE
http.cors.allow-headers : "X-Requested-With,X-Auth-Token,Content-Type, Content-Length, Authorization"

我现在可以运行client.ping调用没有任何错误。