Find out why rate-limiting is not working correctly
bartjkdp opened this issue · comments
This makes sure rate-limiting is being applied as designed, e.g. by using memcache backend. After releasing the new release the following errors occured. In the logs requests are blocked with status code 429:
Rate-limiting should not occur as requests are private endpoints and from logged in users.
Possible explanations:
- The original IP is not determined correctly (check if we pass
X-Forwarded-For
correctly). - Logged in user is not determined correctly.
@CBuiVNG is fixing this in Amsterdam#819