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.
The following are the settings that can be configured for HTTP:
A bind port range. Defaults to
The host address to bind the HTTP service to. Defaults to
The host address to publish for HTTP clients to connect to. Defaults to
Used to set the
The max content of an HTTP request. Defaults
The max length of an HTTP URL. Defaults
The max size of allowed headers. Defaults to
Support for compression when possible (with
Accept-Encoding). Defaults to
Defines the compression level to use.
Enable or disable cross-origin resource sharing,
i.e. whether a browser on another origin can do requests to
Elasticsearch. Defaults to
Which origins to allow. Defaults to
Browsers send a "preflight" OPTIONS-request to
determine CORS settings.
Which methods to allow. Defaults to
Which headers to allow. Defaults to
Enable or disable HTTP pipelining, defaults to
The maximum number of events to be queued up in memory before a HTTP connection is closed, defaults to
It also uses the common network settings.
The http module can be completely disabled and not started by setting
false. This make sense when creating non
data nodes which accept HTTP
requests, and communicate with data nodes using the internal