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

Make all limits configurable #133

Conversation

FinleyMcIlwaine
Copy link
Collaborator

This PR makes all rate limits configurable

@FinleyMcIlwaine FinleyMcIlwaine force-pushed the finley/make-rates-configurable branch 2 times, most recently from 89f6bbb to e052497 Compare July 11, 2024 14:37
@FinleyMcIlwaine FinleyMcIlwaine force-pushed the finley/make-rates-configurable branch from e052497 to 6d63e6a Compare July 11, 2024 14:39
@edsko
Copy link
Collaborator

edsko commented Jul 11, 2024

@kazu-yamamoto We increased the rate limit for pings from 4 to 10 in #108, but we're still seeing some (Java) clients that are exceeding this for some reason. We're also seeing the empty data frames limit being hit. After this PR we can just change these defaults our side, so that's fine, but mentioning it here just in case you feel you want to increase the defaults in http2 itself. We will probably increase it to 100 pings/sec our side, which feels ridiculously high but we prefer to err on the side of not rejecting valid clients versus allowing some (still quite low) load from malicious clients.

@kazu-yamamoto kazu-yamamoto self-requested a review July 11, 2024 20:55
Copy link
Owner

@kazu-yamamoto kazu-yamamoto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.
Note that I don't want to change the default values at this moment.

@kazu-yamamoto kazu-yamamoto merged commit 3a135ff into kazu-yamamoto:main Jul 11, 2024
10 checks passed
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.

3 participants