Open Bedo9041 opened 5 years ago
For v2 Player-API, Player data is cached for 10 minutes per username. Likely it'll be decreased in the future, but for now that is why it does not count as a decrease in rate.
Will be keeping this issue open and locked as it is a legacy bug, though, when v2 is complete, those rates will be fixed.
It appears that requests to the V2 API don't update the rate limit headers correctly if the same resource is requested multiple times in succession.
First request:
Second request:
Third request:
New request to different resource - header is updated to include all previous requests:
Requests to the V1 API seem to have headers more inconsistent than V2.
First request:
Second request - remaining rate limit doesn't change, reset time does:
Third request - remaining rate limit decreases by one, when two requests have been made and reset time change back to the same as the first request:
Fourth request - remaining rate limit jumps down significantly, reset time changes to match second request
It's also worth noting that the headers seem to change between using
x-ratelimit-...
andx-RateLimit-...