---
title: Http input plugin v3.0.10
description: Plugin version: v3.0.10, Released on: 2018-04-06, Changelog. For other versions, see the overview list. To learn more about Logstash, see the Logstash...
url: https://www.elastic.co/docs/reference/logstash/versioned-plugins/v3-0-10-plugins-inputs-http
products:
  - Logstash
applies_to:
  - Elastic Stack: Generally available
---

# Http input plugin v3.0.10
- Plugin version: v3.0.10
- Released on: 2018-04-06
- [Changelog](https://github.com/logstash-plugins/logstash-input-http/blob/v3.0.10/CHANGELOG.md)

For other versions, see the [overview list](https://www.elastic.co/docs/reference/logstash/versioned-plugins/input-http-index).
To learn more about Logstash, see the [Logstash Reference](https://www.elastic.co/guide/en/logstash/current/index.html).

## Getting help

For questions about the plugin, open a topic in the [Discuss](http://discuss.elastic.co) forums. For bugs or feature requests, open an issue in [Github](https://github.com/logstash-plugins/logstash-input-http). For the list of Elastic supported plugins, please consult the [Elastic Support Matrix](https://www.elastic.co/support/matrix#matrix_logstash_plugins).

## Description

Using this input you can receive single or multiline events over http(s). Applications can send an HTTP POST request with a body to the endpoint started by this input and Logstash will convert it into an event for subsequent processing. Users can pass plain text, JSON, or any formatted data and use a corresponding codec with this input. For Content-Type `application/json` the `json` codec is used, but for all other data formats, `plain` codec is used.
This input can also be used to receive webhook requests to integrate with other services and applications. By taking advantage of the vast plugin ecosystem available in Logstash you can trigger actionable events right from your application.

## Blocking Behavior

The HTTP protocol doesn’t deal well with long running requests. This plugin will either return a 429 (busy) error when Logstash is backlogged, or it will time out the request.
If a 429 error is encountered clients should sleep, backing off exponentially with some random jitter, then retry their request.
This plugin will block if the Logstash queue is blocked and there are available HTTP input threads. This will cause most HTTP clients to time out. Sent events will still be processed in this case. This behavior is not optimal and will be changed in a future release. In the future, this plugin will always return a 429 if the queue is busy, and will not time out in the event of a busy queue.

## Security

This plugin supports standard HTTP basic authentication headers to identify the requester. You can pass in a username, password combination while sending data to this input
You can also setup SSL and send data securely over https, with an option of validating the client’s certificate. Currently, the certificate setup is through [Java Keystore format](https://docs.oracle.com/cd/E19509-01/820-3503/ggfen/index.md)

## Http Input Configuration Options

This plugin supports the following configuration options plus the [Common options](#v3.0.10-plugins-inputs-http-common-options) described later.

| Setting                                                               | Input type                                                                                             | Required |
|-----------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|----------|
| [`additional_codecs`](#v3.0.10-plugins-inputs-http-additional_codecs) | [hash](/docs/reference/logstash/plugins/value-types#hash)                                              | No       |
| [`host`](#v3.0.10-plugins-inputs-http-host)                           | [string](/docs/reference/logstash/plugins/value-types#string)                                          | No       |
| [`keystore`](#v3.0.10-plugins-inputs-http-keystore)                   | a valid filesystem path                                                                                | No       |
| [`keystore_password`](#v3.0.10-plugins-inputs-http-keystore_password) | [password](/docs/reference/logstash/plugins/value-types#password)                                      | No       |
| [`password`](#v3.0.10-plugins-inputs-http-password)                   | [password](/docs/reference/logstash/plugins/value-types#password)                                      | No       |
| [`port`](#v3.0.10-plugins-inputs-http-port)                           | [number](/docs/reference/logstash/plugins/value-types#number)                                          | No       |
| [`response_headers`](#v3.0.10-plugins-inputs-http-response_headers)   | [hash](/docs/reference/logstash/plugins/value-types#hash)                                              | No       |
| [`ssl`](#v3.0.10-plugins-inputs-http-ssl)                             | [boolean](/docs/reference/logstash/plugins/value-types#boolean)                                        | No       |
| [`threads`](#v3.0.10-plugins-inputs-http-threads)                     | [number](/docs/reference/logstash/plugins/value-types#number)                                          | No       |
| [`user`](#v3.0.10-plugins-inputs-http-user)                           | [string](/docs/reference/logstash/plugins/value-types#string)                                          | No       |
| [`verify_mode`](#v3.0.10-plugins-inputs-http-verify_mode)             | [string](/docs/reference/logstash/plugins/value-types#string), one of `["none", "peer", "force_peer"]` | No       |

Also see [Common options](#v3.0.10-plugins-inputs-http-common-options) for a list of options supported by all input plugins.

### `additional_codecs`

- Value type is [hash](/docs/reference/logstash/plugins/value-types#hash)
- Default value is `{"application/json"=>"json"}`

Apply specific codecs for specific content types. The default codec will be applied only after this list is checked and no codec for the request’s content-type is found

### `host`

- Value type is [string](/docs/reference/logstash/plugins/value-types#string)
- Default value is `"0.0.0.0"`

The host or ip to bind

### `keystore`

- Value type is [path](/docs/reference/logstash/plugins/value-types#path)
- There is no default value for this setting.

The JKS keystore to validate the client’s certificates

### `keystore_password`

- Value type is [password](/docs/reference/logstash/plugins/value-types#password)
- There is no default value for this setting.

Set the truststore password

### `password`

- Value type is [password](/docs/reference/logstash/plugins/value-types#password)
- There is no default value for this setting.

Password for basic authorization

### `port`

- Value type is [number](/docs/reference/logstash/plugins/value-types#number)
- Default value is `8080`

The TCP port to bind to

### `response_headers`

- Value type is [hash](/docs/reference/logstash/plugins/value-types#hash)
- Default value is `{"Content-Type"=>"text/plain"}`

specify a custom set of response headers

### `ssl`

- Value type is [boolean](/docs/reference/logstash/plugins/value-types#boolean)
- Default value is `false`

SSL Configurations
Enable SSL

### `threads`

- Value type is [number](/docs/reference/logstash/plugins/value-types#number)
- Default value is `4`

Maximum number of threads to use

### `user`

- Value type is [string](/docs/reference/logstash/plugins/value-types#string)
- There is no default value for this setting.

Username for basic authorization

### `verify_mode`

- Value can be any of: `none`, `peer`, `force_peer`
- Default value is `"none"`

Set the client certificate verification method. Valid methods: none, peer, force_peer

## Common options

These configuration options are supported by all input plugins:

| Setting                                                       | Input type                                                      | Required |
|---------------------------------------------------------------|-----------------------------------------------------------------|----------|
| [`add_field`](#v3.0.10-plugins-inputs-http-add_field)         | [hash](/docs/reference/logstash/plugins/value-types#hash)       | No       |
| [`codec`](#v3.0.10-plugins-inputs-http-codec)                 | [codec](/docs/reference/logstash/plugins/value-types#codec)     | No       |
| [`enable_metric`](#v3.0.10-plugins-inputs-http-enable_metric) | [boolean](/docs/reference/logstash/plugins/value-types#boolean) | No       |
| [`id`](#v3.0.10-plugins-inputs-http-id)                       | [string](/docs/reference/logstash/plugins/value-types#string)   | No       |
| [`tags`](#v3.0.10-plugins-inputs-http-tags)                   | [array](/docs/reference/logstash/plugins/value-types#array)     | No       |
| [`type`](#v3.0.10-plugins-inputs-http-type)                   | [string](/docs/reference/logstash/plugins/value-types#string)   | No       |


### `add_field`

- Value type is [hash](/docs/reference/logstash/plugins/value-types#hash)
- Default value is `{}`

Add a field to an event

### `codec`

- Value type is [codec](/docs/reference/logstash/plugins/value-types#codec)
- Default value is `"plain"`

The codec used for input data. Input codecs are a convenient method for decoding your data before it enters the input, without needing a separate filter in your Logstash pipeline.

### `enable_metric`

- Value type is [boolean](/docs/reference/logstash/plugins/value-types#boolean)
- Default value is `true`

Disable or enable metric logging for this specific plugin instance by default we record all the metrics we can, but you can disable metrics collection for a specific plugin.

### `id`

- Value type is [string](/docs/reference/logstash/plugins/value-types#string)
- There is no default value for this setting.

Add a unique `ID` to the plugin configuration. If no ID is specified, Logstash will generate one. It is strongly recommended to set this ID in your configuration. This is particularly useful when you have two or more plugins of the same type, for example, if you have 2 http inputs. Adding a named ID in this case will help in monitoring Logstash when using the monitoring APIs.
```
input {
  http {
    id => "my_plugin_id"
  }
}
```


### `tags`

- Value type is [array](/docs/reference/logstash/plugins/value-types#array)
- There is no default value for this setting.

Add any number of arbitrary tags to your event.
This can help with processing later.

### `type`

- Value type is [string](/docs/reference/logstash/plugins/value-types#string)
- There is no default value for this setting.

Add a `type` field to all events handled by this input.
Types are used mainly for filter activation.
The type is stored as part of the event itself, so you can also use the type to search for it in Kibana.
If you try to set a type on an event that already has one (for example when you send an event from a shipper to an indexer) then a new input will not override the existing type. A type set at the shipper stays with that event for its life even when sent to another Logstash server.