We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
show_kudo_all_button
The Strava API is now throwing a 429: Too Many Requests when using the show_kudo_all_button when doing a lot of requests at the same time. https://developers.strava.com/docs/rate-limits/#:~:text=Requests%20exceeding%20the%20limit%20will,toward%20the%20long%20term%20limit.&text=15%2Dminute%20limit%2C%20followed%20by%20daily%20limit --> it seems like they're now applying the rate limits for their own website too or something. Before this wasn't an issue
Not sure what to do about this one though, perhaps just add a message in the settings to acknowledge this behavior?
HTTP/1.1 429 Too Many Requests Date: Tue, 30 Mar 2021 12:03:41 GMT Content-Type: application/json; charset=utf-8 Connection: keep-alive Cache-Control: no-cache, no-store Via: 1.1 linkerd X-Download-Options: noopen Pragma: no-cache Status: 429 Too Many Requests Expires: Sat, 01 Jan 2000 00:00:00 GMT X-Request-Id: a7f0c33e-f14c-4b69-851e-1b016abe5890 Referrer-Policy: strict-origin-when-cross-origin X-FRAME-OPTIONS: DENY X-Permitted-Cross-Domain-Policies: none X-Content-Type-Options: nosniff X-XSS-Protection: 1; mode=block Content-Length: 19 {"success":"false"}
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The Strava API is now throwing a 429: Too Many Requests when using the
show_kudo_all_button
when doing a lot of requests at the same time.https://developers.strava.com/docs/rate-limits/#:~:text=Requests%20exceeding%20the%20limit%20will,toward%20the%20long%20term%20limit.&text=15%2Dminute%20limit%2C%20followed%20by%20daily%20limit
--> it seems like they're now applying the rate limits for their own website too or something. Before this wasn't an issue
Not sure what to do about this one though, perhaps just add a message in the settings to acknowledge this behavior?
The text was updated successfully, but these errors were encountered: