feat(http1): support configurable max_headers
#3523
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
seanmonstar
requested changes
Jan 12, 2024
|
We encountered an issue that requires this as well, thanks for sending PR! would love to help if needed :) |
wfly1998
force-pushed
the
dyn-header-size
branch
from
f6015e3
to
fed4520
Compare
seanmonstar
reviewed
Jan 24, 2024
Signed-off-by: Yu Li <liyu.yukiteru@bytedance.com>
Signed-off-by: Yu Li <liyu.yukiteru@bytedance.com>
wfly1998
force-pushed
the
dyn-header-size
branch
from
fed4520
to
24bef8e
Compare
wfly1998
added a commit
to wfly1998/hyper-util
that referenced
this pull request
Mar 11, 2024
Adapts configurable `max_headers` from hyperium/hyper#3523.
wfly1998
added a commit
to wfly1998/hyper-util
that referenced
this pull request
Mar 11, 2024
Adapts configurable `max_headers` by hyperium/hyper#3523.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 thathypersets 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_headersto 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.