The http module allows to expose elasticsearch APIs over HTTP.

The http mechanism is completely asynchronous in nature, meaning that there is no blocking thread waiting for a response. The benefit of using asynchronous communication for HTTP is solving the C10k problem.

When possible, consider using HTTP keep alive when connecting for better performance and try to get your favorite client not to do HTTP chunking.


The following are the settings the can be configured for HTTP:

Setting Description


A bind port range. Defaults to 9200-9300.


The max content of an HTTP request. Defaults to 100mb


The max length of an HTTP URL. Defaults to 4kb


Support for compression when possible (with Accept-Encoding). Defaults to false.


Defines the compression level to use. Defaults to 6.


Enable or disable cross-origin resource sharing, i.e. whether a browser on another origin can do requests to Elasticsearch. Defaults to true.


Which origins to allow. Defaults to *, i.e. any origin.


Browsers send a "preflight" OPTIONS-request to determine CORS settings. max-age defines how long the result should be cached for. Defaults to 1728000 (20 days)


Which methods to allow. Defaults to OPTIONS, HEAD, GET, POST, PUT, DELETE.


Which headers to allow. Defaults to X-Requested-With, Content-Type, Content-Length.

It also shares the uses the common network settings.

Disable HTTPedit

The http module can be completely disabled and not started by setting http.enabled to false. This make sense when creating non data nodes which accept HTTP requests, and communicate with data nodes using the internal transport.