Add configurable rate-limits for game endpoints - #1130
Open
Toastbrot236 wants to merge 5 commits into
Open
Toastbrot236 wants to merge 5 commits into
Toastbrot236 wants to merge 5 commits into
Conversation
Toastbrot236
changed the title
Toastbrot236
removed this from the
Get production out of partial read-only mode milestone
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This uses the newly introduced configurable endpoint rate-limiting system on nearly all game endpoints, making them no longer use Bunkum's rate-limit attribute and adding buckets for them to the enum and the config defaults.
This doesn't remove any of the now unused leftover hardcoded constants in
Refresh.Core.RateLimits. That should be done in a PR after this one and a similar PR for API buckets are merged.