-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Comments
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
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
The Http2Settings max header list size setting is ignored by the conversion to the actual Netty settings.
The text was updated successfully, but these errors were encountered: