# Should we get rid of the http.enabled setting

**URL:** <https://discuss.elastic.co/t/should-we-get-rid-of-the-http-enabled-setting/27435>\
**Category:** Elasticsearch\
**Created:** [August 14, 2015, 10:06pm UTC](https://discuss.elastic.co/t/should-we-get-rid-of-the-http-enabled-setting/27435 "2015-08-14T22:06:02Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [August 14, 2015, 10:06pm UTC](https://discuss.elastic.co/t/should-we-get-rid-of-the-http-enabled-setting/27435/1 "2015-08-14T22:06:02Z")

</div>

Having HTTP access to Elasticsearch is critical for both Marvel or other monitoring platforms, the majority of clients and the documentation is predominately built around HTTP Sense examples. Taking that in mind, does it make sense to allow users to set `http.enabled: false`, should we just remove this setting completely?

We've got a github issue open on this, if you'd like to give feedback there or here, we'd be interested in your thoughts.

> <https://github.com/elastic/elasticsearch/issues/12792>

---

<div class="post-metadata">

**Author:** ![mosiddi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mosiddi/32/577_2.png) [@mosiddi](https://discuss.elastic.co/u/mosiddi)\
**Post date:** [August 16, 2015, 9:53am UTC](https://discuss.elastic.co/t/should-we-get-rid-of-the-http-enabled-setting/27435/2 "2015-08-16T09:53:06Z")

</div>

+1 on removing it.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 11:55pm UTC](https://discuss.elastic.co/t/should-we-get-rid-of-the-http-enabled-setting/27435/3 "2017-07-05T23:55:37Z")

</div>