# Http\_max\_content\_length not enforced properly

**URL:** <https://discuss.elastic.co/t/http-max-content-length-not-enforced-properly/170919>\
**Category:** Elastic Cloud Enterprise (ECE)\
**Created:** [March 5, 2019, 1:49pm UTC](https://discuss.elastic.co/t/http-max-content-length-not-enforced-properly/170919 "2019-03-05T13:49:39Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![JamesNotJamez](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jamesnotjamez/32/45736_2.png) [@JamesNotJamez](https://discuss.elastic.co/u/JamesNotJamez)\
**Post date:** [March 5, 2019, 1:49pm UTC](https://discuss.elastic.co/t/http-max-content-length-not-enforced-properly/170919/1 "2019-03-05T13:49:39Z")

</div>

Hi,  
We have the following configuration variable set in a deployment:

```auto
http.max_content_length: "400mb"

```

but when indexing a document are seeing the error

```auto
Caused by: org.elasticsearch.client.ResponseException: POST https://d72ceeb814c740869fafde4e6a89c6d4.dev-eu.elastic.nomura.com:9243/_bulk: HTTP/1.1 413 Request Entity Too Large

Request Content-Length 242874783 exceeds the configured limit of 209715200

```

Looks like the deployment has a configured limit of 200mb despite what is set in the yaml. Wondering if the setting is not being enforced properly?

Additionally is there a way to check the http\_max\_content\_length from within the deployment? Haven't found anything online so far.

Thanks,  
James

---

<div class="post-metadata">

**Author:** ![Alex\_Piggott](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alex_piggott/32/11053_2.png) [@Alex\_Piggott](https://discuss.elastic.co/u/Alex_Piggott)\
**Post date:** [March 5, 2019, 6:23pm UTC](https://discuss.elastic.co/t/http-max-content-length-not-enforced-properly/170919/2 "2019-03-05T18:23:01Z")

</div>

The EC/E proxy places its own limit of 200MB on traffic. This limit is not currently configurable

This is in addition to any limit from `max_content_length` (which apart from the above is applied as you'd expect)

The v2 proxy that is currently being tested and will in due time (no ETA!) replace the current one does _not_ have that limit

Alex

---

<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:** [March 19, 2019, 6:23pm UTC](https://discuss.elastic.co/t/http-max-content-length-not-enforced-properly/170919/3 "2019-03-19T18:23:05Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.