Skip to content
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

HTTP/2 max header list size setting is ignored #4211

Closed
vietj opened this issue Dec 21, 2021 · 0 comments
Closed

HTTP/2 max header list size setting is ignored #4211

vietj opened this issue Dec 21, 2021 · 0 comments
Assignees
Labels
Milestone

Comments

@vietj
Copy link
Member

vietj commented Dec 21, 2021

The Http2Settings max header list size setting is ignored by the conversion to the actual Netty settings.

@vietj vietj added the bug label Dec 21, 2021
@vietj vietj self-assigned this Dec 21, 2021
@vietj vietj added this to the 4.2.3 milestone Dec 21, 2021
vietj added a commit that referenced this issue Dec 21, 2021
…ersion to the actual Netty settings since we only send a setting when the new value is different from the initial value. The initial value is wrong and therefore leads to obtaining the incorrect value.

fixes #4211
vietj added a commit that referenced this issue Dec 21, 2021
…ersion to the actual Netty settings since we only send a setting when the new value is different from the initial value. The initial value is wrong and therefore leads to obtaining the incorrect value.

fixes #4211
vietj added a commit that referenced this issue Dec 21, 2021
…ersion to the actual Netty settings since we only send a setting when the new value is different from the initial value. The initial value is wrong and therefore leads to obtaining the incorrect value.

fixes #4211
vietj added a commit that referenced this issue Dec 21, 2021
…ersion to the actual Netty settings since we only send a setting when the new value is different from the initial value. The initial value is wrong and therefore leads to obtaining the incorrect value.

fixes #4211
vietj added a commit that referenced this issue Dec 21, 2021
…ersion to the actual Netty settings since we only send a setting when the new value is different from the initial value. The initial value is wrong and therefore leads to obtaining the incorrect value.

fixes #4211
vietj added a commit that referenced this issue Dec 21, 2021
…ersion to the actual Netty settings since we only send a setting when the new value is different from the initial value. The initial value is wrong and therefore leads to obtaining the incorrect value.

fixes #4211
@vietj vietj closed this as completed in ed9db7f Dec 21, 2021
vietj added a commit that referenced this issue Dec 21, 2021
…ersion to the actual Netty settings since we only send a setting when the new value is different from the initial value. The initial value is wrong and therefore leads to obtaining the incorrect value.

fixes #4211
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant