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

feat(http2): add config for max_local_error_reset_streams in server #3528

Merged
merged 1 commit into from
Jan 19, 2024

Conversation

Noah-Kennedy
Copy link
Contributor

This change exposes a tunable for the max_local_error_reset_streams parameter in h2.

This change exposes a tunable for the max_local_error_reset_streams parameter in h2.
@Noah-Kennedy
Copy link
Contributor Author

The warnings change was needed because the nightly tests are failing right now due to warnings.

@seanmonstar
Copy link
Member

The warnings change was needed because the nightly tests are failing right now due to warnings.

As in 0.14.x will have warnings from now on?

@Noah-Kennedy
Copy link
Contributor Author

@seanmonstar only on nightly

@seanmonstar seanmonstar merged commit dedcb67 into hyperium:0.14.x Jan 19, 2024
19 checks passed
magurotuna added a commit to magurotuna/hyper that referenced this pull request Nov 14, 2024
The patch hyperium#3528 added the ability for hyper users to configure
`max_local_error_reset_streams` via the server builder to hyper
v0.14.29. It was then pulled in to hyper v1.2.0 as well in hyperium#3530, where
the wrong parameter `max_pending_accept_reset_streams` is passed to h2's
builder as `max_local_error_reset_streams`.

This could lead to significant impact especially when a hyper user does
not set `max_pending_accept_reset_streams`, because its default value is
`None` and passing `None` to h2's `max_local_error_reset_streams` method
will make the server vulnerable to DOS attacks.

This issue has been fixed in this patch, simply by passing the correct
value to the h2's builder method.
seanmonstar pushed a commit that referenced this pull request Nov 15, 2024
The patch #3528 added the ability for hyper users to configure
`max_local_error_reset_streams` via the server builder to hyper
v0.14.29. It was then pulled in to hyper v1.2.0 as well in #3530, where
the wrong parameter `max_pending_accept_reset_streams` is passed to h2's
builder as `max_local_error_reset_streams`.

This could lead to significant impact especially when a hyper user does
not set `max_pending_accept_reset_streams`, because its default value is
`None` and passing `None` to h2's `max_local_error_reset_streams` method
will make the server vulnerable to DOS attacks.

This issue has been fixed in this patch, simply by passing the correct
value to the h2's builder method.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants