WARNING: Version 1.3 of Elasticsearch has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
HTTP
editHTTP
editThe 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.
HTTP pipelining is not supported and should be disabled in your HTTP client.
Settings
editThe following are the settings that can be configured for HTTP:
Setting | Description |
---|---|
|
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
to |
|
The max length of an HTTP URL. Defaults
to |
|
Support for compression when possible (with
Accept-Encoding). Defaults to |
|
Defines the compression level to use.
Defaults to |
|
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
|
It also uses the common network settings.
Disable HTTP
editThe 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.