Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

new steamAPI needs ratelimiting detection #32

Closed
billthecatt opened this issue Sep 20, 2019 · 1 comment
Closed

new steamAPI needs ratelimiting detection #32

billthecatt opened this issue Sep 20, 2019 · 1 comment

Comments

@billthecatt
Copy link

I keep running into this when I'm going through user lists and trying to populate the cache:

In Client.php line 180:

Client error: GET http://api.steampowered.com/IPlayerService/GetRecentlyPlayedGames/v0001/?key=6B264EE334F3233E1B5511D63D0C60D1&format=json&input_json=%7B%22steamId%22%3A %2276561197970845665%22%7D resulted in a 429 Too Many Requests response:

<title>429 Too Many Requests</title>

Too Many Requests

In RequestException.php line 113:

Client error: GET http://api.steampowered.com/IPlayerService/GetRecentlyPlayedGames/v0001/?key=6B264EE334F3233E1B5511D63D0C60D1&format=json&input_json=%7B%22steamId%22%3A %2276561197970845665%22%7D resulted in a 429 Too Many Requests response:

<title>429 Too Many Requests</title>

Too Many Requests

Anyway, would it be possible to create an exception on error 429 from the api call? And then have this enable a holdtown timer and have the script wait x seconds before trying again?

Thanks,

billcat

@ilumos ilumos closed this as completed in 6ad33cf May 13, 2020
@ilumos
Copy link
Contributor

ilumos commented May 13, 2020

I've implemented rate limiting to match Steam's 200 requests every 5 minutes, and in testing all seems well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants