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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/ebe1182d-995e-4a22-9411-076b3191173f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to