# ES 2.3 - http.max.content.length and http.max\_initial\_line\_length

**URL:** <https://discuss.elastic.co/t/es-2-3-http-max-content-length-and-http-max-initial-line-length/56191>\
**Category:** Elasticsearch\
**Created:** [July 22, 2016, 2:55pm UTC](https://discuss.elastic.co/t/es-2-3-http-max-content-length-and-http-max-initial-line-length/56191 "2016-07-22T14:55:19Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![lhorsky1](https://avatars.discourse-cdn.com/v4/letter/l/b2d939/32.png) [@lhorsky1](https://discuss.elastic.co/u/lhorsky1)\
**Post date:** [July 22, 2016, 2:55pm UTC](https://discuss.elastic.co/t/es-2-3-http-max-content-length-and-http-max-initial-line-length/56191/1 "2016-07-22T14:55:19Z")

</div>

In ES2.3, is it still necessary to set http.max.content.length and http.max\_initial\_line\_length higher to handle large Kibana queries?

In 1.5, we set these to 1000mb and 400kb respectively to prevent issues with Kibana and Elasticsearch when users executed queries that would have large #s of results.

---

<div class="post-metadata">

**Author:** ![DiscussBuster](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/discussbuster/32/11042_2.png) [@DiscussBuster](https://discuss.elastic.co/u/DiscussBuster)\
**Post date:** [July 25, 2016, 1:09am UTC](https://discuss.elastic.co/t/es-2-3-http-max-content-length-and-http-max-initial-line-length/56191/2 "2016-07-25T01:09:42Z")

</div>

[Here](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-http.html#_settings_2)

---

<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, 10:33pm UTC](https://discuss.elastic.co/t/es-2-3-http-max-content-length-and-http-max-initial-line-length/56191/3 "2017-07-05T22:33:17Z")

</div>