# ES 1.4.4 with Marvel latest throws exception in Chrome
**URL:** https://discuss.elastic.co/t/es-1-4-4-with-marvel-latest-throws-exception-in-chrome/22365
**Category:** Elasticsearch
**Created:** [February 24, 2015, 10:16pm UTC](https://discuss.elastic.co/t/es-1-4-4-with-marvel-latest-throws-exception-in-chrome/22365 "2015-02-24T22:16:33Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@Jay\_Hilden](https://discuss.elastic.co/u/Jay_Hilden)
#### Post date: [February 24, 2015, 10:16pm UTC](https://discuss.elastic.co/t/es-1-4-4-with-marvel-latest-throws-exception-in-chrome/22365/1 "2015-02-24T22:16:33Z")
I am on a Windows 8 PC and I downloaded ES 1.4.4, installed Marvel's latest
version, and started ES. ES starts up just fine but when I tried to view
marvel I get an exception within ES:
[2015-02-24 16:10:14,462][WARN][http.netty] [Kid Nova]
Caught exception while handling client http traffic, closing connection
[id: 0xc3000144, /0:0:0:0:0:0:0:1:51607 =\> /0:0:0:0:0:0:0:1:9200]
org.elasticsearch.common.netty.handler.codec.frame.TooLongFrameException:
HTTP header is larger than 8192 bytes.
The only thing that I changed was the cluster name in the .yml file,
nothing else was touched.
This exception happens in Chrome, in FF Developer Edition it runs just
fine.
What's up with that?
--
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/498c3032-5108-4318-b443-b2c2bae60c78%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/498c3032-5108-4318-b443-b2c2bae60c78%40googlegroups.com).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@Boaz\_Leskes](https://discuss.elastic.co/u/Boaz_Leskes)
#### Post date: [February 25, 2015, 7:33am UTC](https://discuss.elastic.co/t/es-1-4-4-with-marvel-latest-throws-exception-in-chrome/22365/2 "2015-02-25T07:33:49Z")
Hi Jay,
There is a setting to increase that limit, but I want to understand what's
happening as it is unexpected. Can you open up the developer tools in
Chrome and check the headers of the failed request? I wonder what it is
that is so long.
Cheers,
Boaz
On Tuesday, February 24, 2015 at 11:16:33 PM UTC+1, Jay Hilden wrote:
> I am on a Windows 8 PC and I downloaded ES 1.4.4, installed Marvel's
> latest version, and started ES. ES starts up just fine but when I tried to
> view marvel I get an exception within ES:
>
> [2015-02-24 16:10:14,462][WARN][http.netty] [Kid Nova]
> Caught exception while handling client http traffic, closing connection
> [id: 0xc3000144, /0:0:0:0:0:0:0:1:51607 =\> /0:0:0:0:0:0:0:1:9200]
> org.elasticsearch.common.netty.handler.codec.frame.TooLongFrameException:
> HTTP header is larger than 8192 bytes.
>
> The only thing that I changed was the cluster name in the .yml file,
> nothing else was touched.
>
> This exception happens in Chrome, in FF Developer Edition it runs just
> fine.
>
> What's up with that?
--
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/726ddbf8-4337-4f72-bb23-12c040c38941%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/726ddbf8-4337-4f72-bb23-12c040c38941%40googlegroups.com).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@Jay\_Hilden](https://discuss.elastic.co/u/Jay_Hilden)
#### Post date: [February 25, 2015, 4:25pm UTC](https://discuss.elastic.co/t/es-1-4-4-with-marvel-latest-throws-exception-in-chrome/22365/3 "2015-02-25T16:25:03Z")
Boaz, here is the output from fiddler.
On Wednesday, February 25, 2015 at 1:33:50 AM UTC-6, Boaz Leskes wrote:
> Hi Jay,
>
> There is a setting to increase that limit, but I want to understand what's
> happening as it is unexpected. Can you open up the developer tools in
> Chrome and check the headers of the failed request? I wonder what it is
> that is so long.
>
> Cheers,
> Boaz, I found the culprit, I had cookies with the domain of localhost that
> must have been longer than 8192 because once I cleared those it worked fine.
Out of curiosity, why is there a restriction on header at 8192?
> On Tuesday, February 24, 2015 at 11:16:33 PM UTC+1, Jay Hilden wrote:
>
> > I am on a Windows 8 PC and I downloaded ES 1.4.4, installed Marvel's
> > latest version, and started ES. ES starts up just fine but when I tried to
> > view marvel I get an exception within ES:
> >
> > [2015-02-24 16:10:14,462][WARN][http.netty] [Kid Nova]
> > Caught exception while handling client http traffic, closing connection
> > [id: 0xc3000144, /0:0:0:0:0:0:0:1:51607 =\> /0:0:0:0:0:0:0:1:9200]
> > org.elasticsearch.common.netty.handler.codec.frame.TooLongFrameException:
> > HTTP header is larger than 8192 bytes.
> >
> > The only thing that I changed was the cluster name in the .yml file,
> > nothing else was touched.
> >
> > This exception happens in Chrome, in FF Developer Edition it runs just
> > fine.
> >
> > What's up with that?
--
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/ae47082d-3a3f-4bc7-866d-39b0fa5914aa%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ae47082d-3a3f-4bc7-866d-39b0fa5914aa%40googlegroups.com).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@Jay\_Hilden](https://discuss.elastic.co/u/Jay_Hilden)
#### Post date: [February 25, 2015, 4:25pm UTC](https://discuss.elastic.co/t/es-1-4-4-with-marvel-latest-throws-exception-in-chrome/22365/4 "2015-02-25T16:25:43Z")
> Boaz, I found the culprit, I had cookies with the domain of localhost that
> must have been longer than 8192 because once I cleared those it worked fine.
Out of curiosity, why is there a restriction on header at 8192?
On Wednesday, February 25, 2015 at 1:33:50 AM UTC-6, Boaz Leskes wrote:
> Hi Jay,
>
> There is a setting to increase that limit, but I want to understand what's
> happening as it is unexpected. Can you open up the developer tools in
> Chrome and check the headers of the failed request? I wonder what it is
> that is so long.
>
> Cheers,
> Boaz
>
> On Tuesday, February 24, 2015 at 11:16:33 PM UTC+1, Jay Hilden wrote:
>
> > I am on a Windows 8 PC and I downloaded ES 1.4.4, installed Marvel's
> > latest version, and started ES. ES starts up just fine but when I tried to
> > view marvel I get an exception within ES:
> >
> > [2015-02-24 16:10:14,462][WARN][http.netty] [Kid Nova]
> > Caught exception while handling client http traffic, closing connection
> > [id: 0xc3000144, /0:0:0:0:0:0:0:1:51607 =\> /0:0:0:0:0:0:0:1:9200]
> > org.elasticsearch.common.netty.handler.codec.frame.TooLongFrameException:
> > HTTP header is larger than 8192 bytes.
> >
> > The only thing that I changed was the cluster name in the .yml file,
> > nothing else was touched.
> >
> > This exception happens in Chrome, in FF Developer Edition it runs just
> > fine.
> >
> > What's up with that?
--
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/807b6194-3b82-40ab-b2b4-28bbd1004809%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/807b6194-3b82-40ab-b2b4-28bbd1004809%40googlegroups.com).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@Boaz\_Leskes](https://discuss.elastic.co/u/Boaz_Leskes)
#### Post date: [February 25, 2015, 7:10pm UTC](https://discuss.elastic.co/t/es-1-4-4-with-marvel-latest-throws-exception-in-chrome/22365/5 "2015-02-25T19:10:42Z")
Great.
This is a netty settings but I would speculate it's built in order to
protect from a single, malicious request from using huge amounts of memory.
On Wednesday, February 25, 2015 at 5:25:44 PM UTC+1, Jay Hilden wrote:
> Boaz, I found the culprit, I had cookies with the domain of localhost that
>
> > must have been longer than 8192 because once I cleared those it worked fine.
>
> Out of curiosity, why is there a restriction on header at 8192?
>
> On Wednesday, February 25, 2015 at 1:33:50 AM UTC-6, Boaz Leskes wrote:
>
> > Hi Jay,
> >
> > There is a setting to increase that limit, but I want to understand
> > what's happening as it is unexpected. Can you open up the developer tools
> > in Chrome and check the headers of the failed request? I wonder what it is
> > that is so long.
> >
> > Cheers,
> > Boaz
> >
> > On Tuesday, February 24, 2015 at 11:16:33 PM UTC+1, Jay Hilden wrote:
> >
> > > I am on a Windows 8 PC and I downloaded ES 1.4.4, installed Marvel's
> > > latest version, and started ES. ES starts up just fine but when I tried to
> > > view marvel I get an exception within ES:
> > >
> > > [2015-02-24 16:10:14,462][WARN][http.netty] [Kid Nova]
> > > Caught exception while handling client http traffic, closing connection
> > > [id: 0xc3000144, /0:0:0:0:0:0:0:1:51607 =\> /0:0:0:0:0:0:0:1:9200]
> > > org.elasticsearch.common.netty.handler.codec.frame.TooLongFrameException:
> > > HTTP header is larger than 8192 bytes.
> > >
> > > The only thing that I changed was the cluster name in the .yml file,
> > > nothing else was touched.
> > >
> > > This exception happens in Chrome, in FF Developer Edition it runs just
> > > fine.
> > >
> > > What's up with that?
--
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/ebe1182d-995e-4a22-9411-076b3191173f%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ebe1182d-995e-4a22-9411-076b3191173f%40googlegroups.com).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 12:30am UTC](https://discuss.elastic.co/t/es-1-4-4-with-marvel-latest-throws-exception-in-chrome/22365/6 "2017-07-06T00:30:06Z")