Rate limiting #136

Closed
opened 2025-10-03 04:44:53 -05:00 by konstkarapan · 4 comments
konstkarapan commented 2025-10-03 04:44:53 -05:00 (Migrated from github.com)

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:

### 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:
notquitenothing commented 2025-10-28 22:31:56 -05:00 (Migrated from github.com)

While this would be possible to implement, I believe this should be done in your reverse proxy if possible.

While this would be possible to implement, I believe this should be done in your reverse proxy if possible.
notquitenothing commented 2025-12-22 12:26:12 -06:00 (Migrated from github.com)

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.)

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.)
notquitenothing commented 2025-12-31 11:50:34 -06:00 (Migrated from github.com)

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.

This is released in [v1.8.0](https://github.com/voidauth/voidauth/releases/tag/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.
notquitenothing commented 2026-01-02 19:28:11 -06:00 (Migrated from github.com)

Assumed resolved in v1.8.0 . Please re-open if it is not

Assumed resolved in v1.8.0 . Please re-open if it is not
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
adam/gate#136
No description provided.