Make a lot of simultaneous requests (concurrency > 5, I've able to reproduce both failure cases with concurrency = 20) to https://login.eveonline.com/v2/oauth/token with correct refresh_token
Actual Behaviour
1) Refreshing access token sometimes fails with error 500: {"Message":"An error has occurred."}
2) Eventually keep-alive connection gets reset.
Expected Behaviour
All of the requests successfully obtain new access tokens
Notes
I understand that this endpoint needs to be rate-limited for security reasons, but if refresh_token is valid, it should not apply to rate limits. If this is not possible to implement, at least make rate limits known.
Bug
Reproduction Steps
Make a lot of simultaneous requests (concurrency > 5, I've able to reproduce both failure cases with concurrency = 20) to https://login.eveonline.com/v2/oauth/token with correct refresh_token
Actual Behaviour
1) Refreshing access token sometimes fails with error 500: {"Message":"An error has occurred."} 2) Eventually keep-alive connection gets reset.
Expected Behaviour
All of the requests successfully obtain new access tokens
Notes
I understand that this endpoint needs to be rate-limited for security reasons, but if refresh_token is valid, it should not apply to rate limits. If this is not possible to implement, at least make rate limits known.