# JSON codec plugin - target option (http input)

**URL:** <https://discuss.elastic.co/t/json-codec-plugin-target-option-http-input/304217>\
**Category:** Logstash\
**Created:** [May 9, 2022, 8:04am UTC](https://discuss.elastic.co/t/json-codec-plugin-target-option-http-input/304217 "2022-05-09T08:04:41Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [May 9, 2022, 2:26pm UTC](https://discuss.elastic.co/t/json-codec-plugin-target-option-http-input/304217/4 "2022-05-09T14:26:07Z")

</div>

> [@sectex](#):
>
> `Content-Type: application/json`

That feels like a bug to me. The input applies a codec itself before seeing what codec the user configured. See [here](https://github.com/logstash-plugins/logstash-input-http/blob/9fb2f674a97be34acde2c7d234d13de914cf5a84/lib/logstash/inputs/http.rb#L99). You could try

```
additional_codecs => {}
codec => json { target => "[document]" }

```

---

_[View the full topic](https://discuss.elastic.co/t/json-codec-plugin-target-option-http-input/304217)._