AspNetCoreRateLimit
AspNetCoreRateLimit copied to clipboard
Number of counter store entries for single /64 prefix in IPv6
If I use the approach of Rate limiting based on client IP as described in the readme, how many entries will be in the counter store after handling requests from IPv6 addresses in a single /64 prefix?
Bump!
Ip rate limiting on unauthenticated routes makes no sense, unless you count requests coming from /64 prefixes as one "source", as attackers can easily spoof quintillions of different IPv6 addresses within their prefix.
I am therefor also interested how this package treats IPv6 addresses!