Skip to content
This repository has been archived by the owner on Jan 13, 2021. It is now read-only.

Rate Limiting Issues With I2P Accesss #485

Open
bonedaddy opened this issue May 6, 2020 · 2 comments
Open

Rate Limiting Issues With I2P Accesss #485

bonedaddy opened this issue May 6, 2020 · 2 comments
Labels
type:bug Something isn't working

Comments

@bonedaddy
Copy link
Contributor

Describe the bug
When users access our service via I2P, all access to the API will appear to be coming from the LAN IP address of our I2P router, as opposed to an actual client IP.

Expected behavior

  • Dont rate limit I2P users since I2P essentially acts as a "rate limit" anyways.

I'm not quite sure how to solve this without increasing per-IP rate limits.

@bonedaddy bonedaddy added the type:bug Something isn't working label May 6, 2020
@xiegeo
Copy link
Contributor

xiegeo commented May 7, 2020

White list LAN IP addresses?

@bonedaddy
Copy link
Contributor Author

Good idea, i think that's possible with the rate limiter we use? I will check

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type:bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants