-
-
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
feat(http1): support configurable max_headers
#3523
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the thorough PR! I welcome adding the option, but I want to make sure we continue to stay as fast as possible.
We encountered an issue that requires this as well, thanks for sending PR! would love to help if needed :) |
f6015e3
to
fed4520
Compare
Signed-off-by: Yu Li <[email protected]>
Signed-off-by: Yu Li <[email protected]>
fed4520
to
24bef8e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Phenomenal work!
Adapts configurable `max_headers` from hyperium/hyper#3523.
Adapts configurable `max_headers` by hyperium/hyper#3523.
Backport hyperium#3523 to 0.14.x.
Recently we encountered a problem when using
hyper
.After the client sent the request, it received response
431 Request Header Fields Too Large
. After investigation, we found thathyper
sets an upper limit on the number ofheaders
, and this upper limit is a fixed and non-configurable value.#3283 also encountered similar problems.
This PR sets
max_headers
to a configurable value. Its default value remains the same as the previous code, and we can set this value when needed.Additionally, unit tests have been added and the current code passes.