-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
What's the maximum header size limit? #3283
Comments
To be more specific, are you asking about the list of headers, or the length of any single header? If receiving a lot of headers, the current limit of name/value pairs in hyper is 100. That was picked somewhat arbitrarily, and could be increased if more than that were common, but so far no one has ever needed it 🤷 . |
Thanks for this. I can't tell you what's right but it seems Firefox, Chrome (and curl) all accept name/value pairs all the way until they reach the maximum response header size. Which seems to be limited to somewhere between 256KB and 1MB. |
I'm not sure about client-side, but Apache httpd 2.4's default |
Does this MAX_HEADERS of 100 also apply for http2 requests (server-side)? |
No, that limit is for the HTTP/1 decoder. HTTP/2 has a setting that you can send, |
I ran into the same problem (message head is too large) for reqwest and I found my way here to this thread. |
need to be increased or can be configurable. |
Hi, we've encountered same problem here. Our HTTP request has 100+ headers and hyper failed with error. Is there any plan to make it configurable? |
I think this was resolved in #3523 but the issue seems to have been left open |
Good call, thanks for connecting the issue! |
Version
current from master
Platform
Linux
Description
I'm using hyper in curl, and when I receive a HTTP/1 response with many response headers, hyper cuts off the response and returns an error due to
message head is too large
. (With aHYPERE_INVALID_PEER_MESSAGE
error)I cannot find what this exact limit is. I can't even find it in the hyper source code.
The text was updated successfully, but these errors were encountered: