# Possible problem in yml config file

**URL:** <https://discuss.elastic.co/t/possible-problem-in-yml-config-file/19173>\
**Category:** Elasticsearch\
**Created:** [August 8, 2014, 11:48pm UTC](https://discuss.elastic.co/t/possible-problem-in-yml-config-file/19173 "2014-08-08T23:48:12Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sitkawoof](https://avatars.discourse-cdn.com/v4/letter/s/47e85d/32.png) [@Sitkawoof](https://discuss.elastic.co/u/Sitkawoof)\
**Post date:** [August 8, 2014, 11:48pm UTC](https://discuss.elastic.co/t/possible-problem-in-yml-config-file/19173/1 "2014-08-08T23:48:12Z")

</div>

I was doing a PUT to ES and got this error:

org.elasticsearch.common.netty.handler.codec.frame.TooLongFrameException:  
An HTTP line is larger than 4096 bytes.

I checked the message and it was indeed larger than 4096. So I went to  
elasticsearch.yml config file and found:

# Set a custom allowed content length:

# 

# http.max\_content\_length: 100mb

in the section configuring the HTTP ports. I uncommented the line can made  
the number smaller and saved. Stopped ES and restarted it.  
Did the same PUT again. Got the same error. Leads me to believe this  
parameter is not correctly being processed at start up.

Anyone out there had the same experience and found another fix for it?

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/5b075fb6-cb9a-4fa3-8572-421f40b183c7%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5b075fb6-cb9a-4fa3-8572-421f40b183c7%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [August 9, 2014, 2:54am UTC](https://discuss.elastic.co/t/possible-problem-in-yml-config-file/19173/2 "2014-08-09T02:54:00Z")

</div>

Check indentation. YAML is very sensible.

So if you have:

cluster.name: bla  
http.max\_content\_length: 100mb

The later won't be applied. It must be:  
cluster.name: bla  
http.max\_content\_length: 100mb

--  
David 😉  
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 9 août 2014 à 01:48, Sitka [sitkawoof@gmail.com](mailto:sitkawoof@gmail.com) a écrit :

I was doing a PUT to ES and got this error:

org.elasticsearch.common.netty.handler.codec.frame.TooLongFrameException: An HTTP line is larger than 4096 bytes.

I checked the message and it was indeed larger than 4096. So I went to elasticsearch.yml config file and found:

# Set a custom allowed content length:

# 

# http.max\_content\_length: 100mb

in the section configuring the HTTP ports. I uncommented the line can made the number smaller and saved. Stopped ES and restarted it.  
Did the same PUT again. Got the same error. Leads me to believe this parameter is not correctly being processed at start up.

Anyone out there had the same experience and found another fix for it?

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/5b075fb6-cb9a-4fa3-8572-421f40b183c7%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5b075fb6-cb9a-4fa3-8572-421f40b183c7%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CEE95014-8CD3-4924-94D8-3966A396F9D8%40pilato.fr](https://groups.google.com/d/msgid/elasticsearch/CEE95014-8CD3-4924-94D8-3966A396F9D8%40pilato.fr).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![Sitkawoof](https://avatars.discourse-cdn.com/v4/letter/s/47e85d/32.png) [@Sitkawoof](https://discuss.elastic.co/u/Sitkawoof)\
**Post date:** [August 11, 2014, 6:11pm UTC](https://discuss.elastic.co/t/possible-problem-in-yml-config-file/19173/3 "2014-08-11T18:11:59Z")

</div>

indentation is okay so that' not it.

On Fri, Aug 8, 2014 at 7:54 PM, David Pilato [david@pilato.fr](mailto:david@pilato.fr) wrote:

> Check indentation. YAML is very sensible.
> 
> So if you have:
> 
> cluster.name: bla  
> http.max\_content\_length: 100mb
> 
> The later won't be applied. It must be:  
> cluster.name: bla  
> http.max\_content\_length: 100mb
> 
> --  
> David 😉  
> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> 
> Le 9 août 2014 à 01:48, Sitka [sitkawoof@gmail.com](mailto:sitkawoof@gmail.com) a écrit :
> 
> I was doing a PUT to ES and got this error:
> 
> org.elasticsearch.common.netty.handler.codec.frame.TooLongFrameException:  
> An HTTP line is larger than 4096 bytes.
> 
> I checked the message and it was indeed larger than 4096. So I went to  
> elasticsearch.yml config file and found:
> 
> # Set a custom allowed content length:
> 
> # 
> 
> # http.max\_content\_length: 100mb
> 
> in the section configuring the HTTP ports. I uncommented the line can  
> made the number smaller and saved. Stopped ES and restarted it.  
> Did the same PUT again. Got the same error. Leads me to believe this  
> parameter is not correctly being processed at start up.
> 
> Anyone out there had the same experience and found another fix for it?
> 
> --  
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
> 
> To view this discussion on the web visit  
> [https://groups.google.com/d/msgid/elasticsearch/5b075fb6-cb9a-4fa3-8572-421f40b183c7%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5b075fb6-cb9a-4fa3-8572-421f40b183c7%40googlegroups.com)  
> [https://groups.google.com/d/msgid/elasticsearch/5b075fb6-cb9a-4fa3-8572-421f40b183c7%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/5b075fb6-cb9a-4fa3-8572-421f40b183c7%40googlegroups.com?utm_medium=email&utm_source=footer)  
> .  
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
> 
> --  
> You received this message because you are subscribed to a topic in the  
> Google Groups "elasticsearch" group.  
> To unsubscribe from this topic, visit  
> [https://groups.google.com/d/topic/elasticsearch/BOOtBYLuDSs/unsubscribe](https://groups.google.com/d/topic/elasticsearch/BOOtBYLuDSs/unsubscribe).  
> To unsubscribe from this group and all its topics, send an email to  
> [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> To view this discussion on the web visit  
> [https://groups.google.com/d/msgid/elasticsearch/CEE95014-8CD3-4924-94D8-3966A396F9D8%40pilato.fr](https://groups.google.com/d/msgid/elasticsearch/CEE95014-8CD3-4924-94D8-3966A396F9D8%40pilato.fr)  
> [https://groups.google.com/d/msgid/elasticsearch/CEE95014-8CD3-4924-94D8-3966A396F9D8%40pilato.fr?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CEE95014-8CD3-4924-94D8-3966A396F9D8%40pilato.fr?utm_medium=email&utm_source=footer)  
> .
> 
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAChkSb%2BKDSnEUm7gJOvji9dzEYiJi-rGo%2Bmv7DY8tY6NYFmu%2Bw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAChkSb%2BKDSnEUm7gJOvji9dzEYiJi-rGo%2Bmv7DY8tY6NYFmu%2Bw%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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 6, 2017, 1:09am UTC](https://discuss.elastic.co/t/possible-problem-in-yml-config-file/19173/4 "2017-07-06T01:09:32Z")

</div>


