Allow the client to be initialized with a path prefix about elasticsearch-js HOT 4 CLOSED

Yep, the host objects closely mimic the object that node's http.request accepts as it's argument. I'm surprised that I didn't write docs for those objects; it is on my TODO list now.

In the mean time, here is a detailed list of all the keys you can use to describe a host and their defaults:

var client = new elasticsearch.Client({
  hosts: [
    {
      protocol: 'http',
      host: 'localhost', // can also be hostname: 
      path: '/', // can also be pathname:
      port: 9200,
      auth: null, // Basic authentication i.e. 'user:password' to compute an Authorization header.
      query: null, // query string, or an object which will be serialized to a query string
      headers: null // object, this is only supported in node and es.jquery.js, expect full support soon
    }
  ]
});

from elasticsearch-js.

I do understand that instead of trying something like:

host: {
    protocol: 'http',
    host: 'my.apigee.com',
    prefix: 'v1/proxy' // bogus, made up by me
}

I can use http://my.apigee.com/v1/proxy to get the desired effect today.

I am just curious if it can be done in a cleaner fashion like upstairs as well?

from elasticsearch-js.

Sure thing. Instead of using the prefix: key, use the path: key to accomplish this.

from elasticsearch-js.

thanks @spenceralger is there somethign for placing headers as well? where can the docs be updated to reflect path and header configurations?

from elasticsearch-js.