Identify Users by PantryID for Rate Limiting #153
Merged
Conversation
This file contains 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
When applying rate-limiting to a api endpoint, we need to identify users by a pantryID. By not uniquely identifying users, all users will be rate limited after the request threshold is reached by a user. This change addresses the need by: * Passing the pantryID as the key to the rate-limiting middleware
imRohan
added
the
Ready for Review
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When applying rate-limiting to a api endpoint, we need to identify users
by a pantryID. By not uniquely identifying users, all users will be rate
limited after the request threshold is reached by a user.
This change addresses the need by: