Roman

Results 72 comments of Roman

Limit not working? Rate Limit not honored as the Request Volumes Increase

This package uses Get/Set approach, which is vulnerable on high traffic. Similar vulnerability was found on `express-brute` package. [rate-limiter-flexible](https://github.com/animir/node-rate-limiter-flexible) package implements atomic increments.

key column length (256 chars) makes problem in long key rate limitation in postgres

@KeyvanArj Hey, that's interesting case, thank you for reporting. While SHA-256 solution is good, there is another one I could suggest. Database table can be created separately from `RateLimiterPostgres` with...

key column length (256 chars) makes problem in long key rate limitation in postgres

Closing this, since it is not a bug and there are at least two ways to solve this edge case.

Feature: Support for worker threads

@ronag Hey, thank you for the idea. Let us know, if you are going to implement it.

Feature: Support for worker threads

Closing this, since nobody works on it.

Implement SQLite3 limiter class

This package does not support SQLite3 yet. `knex` is supported but only for MySQL and PostgreSQL limiters now. I believe, MySQL related limiter queries and approach is the most close...

Implement SQLite3 limiter class

Closing due to inactivity

Implement SQLite3 limiter class

@mihilmy Hey, nobody started contributing on this one.

How To Rate Limit When Multiple Users are from the Same IP Address?

@szarkowicz Hi, you can rate limit your API only if you have some unique keys. It may be IP address, but you don't want to use it. Can you use...

How To Rate Limit When Multiple Users are from the Same IP Address?

@szarkowicz This is going to be a little more complex. You should make that user ID. Provide public access to API endpoint, only if user has one. For that, there...