-
Notifications
You must be signed in to change notification settings - Fork 24.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
maxHeaderSize is exceeding default value of 8192bytes and causing exception #5665
Comments
Hi @schmorgs, you should be able to configure this with: http.max_header_size: 16kb In elasticsearch.yml Closing this for now, if you need to follow up the mailing list is probably the best place for questions like this: https://groups.google.com/forum/?fromgroups#!forum/elasticsearch |
Excellent, thank you so much. I’ve spent 4 hours today looking at how to solve this :) From: Lee Hinman [mailto:notifications@github.com] Hi @schmorgs https://github.com/schmorgs , you should be able to configure this with: http.max_header_size: 16kb In elasticsearch.yml Closing this for now, if you need to follow up the mailing list is probably the best place for questions like this: https://groups.google.com/forum/?fromgroups#!forum/elasticsearch — |
Thanks!
|
I'm using Elasticsearch behind an Apache reverse proxy, coupled with VAS authentication.
On certain occasions, the header size is exceeding 8192 bytes (error below) and ES throws an exception which causes the request to fail.
It looks like maxHeaderSize in the netty module is defaulting to 8192 bytes, but I can't find any way of overriding (increasing) this value, and if not, can it be added as a configurable parameter in the yml file?
[2014-04-02 08:42:11,500][WARN ][http.netty ] [xxxxx] Caught exception while handling client http traffic, closing connection [id: 0x121a4d3d, /127.0.0.1:33167 => /127.0.0.1:9200]
org.elasticsearch.common.netty.handler.codec.frame.TooLongFrameException: HTTP header is larger than 8192 bytes.
at org.elasticsearch.common.netty.handler.codec.http.HttpMessageDecoder.readHeader(HttpMessageDecoder.java:596)
The text was updated successfully, but these errors were encountered: