Rate limiting #136
Labels
No labels
bug
chore
documentation
enhancement
help
in-progress
question
ready-for-release
released
translation
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
adam/gate#136
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Describe your idea for an enhancement:
Is it possible to add a setting for rate limiting the login page? I'm not into coding so I don't know whether this is easy to implement, but I thought it would be a nice addition
Describe alternatives you've considered:
Additional context:
While this would be possible to implement, I believe this should be done in your reverse proxy if possible.
I do think that rate limiting specific endpoints is a good idea that I need to implement. Specifically those that produce database entries or tax hardware (password resets, signups, session-creation, etc.)
This is released in v1.8.0 as the API_RATELIMIT environment variable, which applies a rate limit to all mutating (POST-PATCH-PUT-DELETE) requests. This should include all authenticated-session-creating actions as well creation of things like password resets, verification emails, etc.
Assumed resolved in v1.8.0 . Please re-open if it is not