Open
Conversation
|
The preview deployment is in progress. 🟡 Last updated at: 2025-07-07 21:29:06 CET |
Contributor
Author
|
At this stage the PR is pretty useless, nothing is made that can make use of a rate limiter. I advise watching this video from ExlixirCasts to better understand how to use this lib. |
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
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.
A Plug for rate limiting requests by IP address and user ID using Hammer.
How It Works
# {@ip_limit}requests per# {@interval}ms.conn.assigns[:current_user_id]) to# {@user_limit}requests per# {@interval}ms.429 Too Many Requestsresponse.This plug expects
conn.assigns[:current_user_id]to be set by an authentication plug earlier in the pipeline.If not present, the plug will default to treating the user as
"anon".