Imgur API-获取“太多请求"错误,即使"X-Ratelimit-Userremaining"不为0 [英] Imgur API - Getting "Too many Request" error even though 'X-Ratelimit-Userremaining' is not 0

查看:168
本文介绍了Imgur API-获取“太多请求"错误,即使"X-Ratelimit-Userremaining"不为0的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在通过Imgur API上传图像( https://apidocs.imgur.com/)但我什至以为先前的请求返回了"X-Ratelimit-Userremaining = 1216",因此收到了太多请求"(错误429).我的理解是,在达到速率限制之前,我应该能够执行1216 POST.

I am uploading images through the Imgur API (https://apidocs.imgur.com/) but I am getting a 'Too many Request' (err 429) even thought the previous request returned 'X-Ratelimit-Userremaining=1216'. My understanding is that I should be able to do 1216 POST before hitting the rate limit.

第一个请求标头(成功)

First request header (success)

X-Ratelimit-Userlimit ,Value : [2000]
X-Post-Rate-Limit-Reset ,Value : [1099]
X-Ratelimit-Clientreset ,Value : [11017]
X-Ratelimit-Userreset ,Value : [3600]
X-Ratelimit-Userremaining ,Value : [1216]
X-Post-Rate-Limit-Remaining ,Value : [1244]
X-Ratelimit-Clientlimit ,Value : [12500]
X-Post-Rate-Limit-Limit ,Value : [1250]
X-Ratelimit-Clientremaining ,Value : [12248]
Content-Type ,Value : [application/json]

第二个请求标头(失败,达到速率限制):

Second request headers (fail, rate limit hit):

X-Ratelimit-Userlimit ,Value : [2000]
X-Ratelimit-Clientreset ,Value : [10204]
X-Ratelimit-Userreset ,Value : [3600]
X-Ratelimit-Userremaining ,Value : [0]
X-Ratelimit-Clientlimit ,Value : [12500]
X-Ratelimit-Clientremaining ,Value : [12035]
Content-Type ,Value : [application/vnd.imgur.v1+json]

推荐答案

请查看 https://apidocs.imgur.com/#rate-limits ,您可以在其中找到有关特定API速率限制的详细信息.

Please take a look at https://apidocs.imgur.com/#rate-limits where you'll find detailed information about specific API rate limits.

Imgur具有多个速率限制,包括每个应用程序和用户IP限制.即使您有更多的用户请求信用,该应用程序也将不再有可用的信用,这可能会触发您的请求的费率限制.

Imgur has multiple rate limits including per application and user IP limits. Even if you have more user request credits, the application can have no more credits available, and that might trigger the rate limit for your requests.

每个来自Imgur服务器的响应都包含速率限制标题,这些标题将为您提供有关所达到的限制的更多详细信息.

Each response from the Imgur servers contains rate limit headers that will give you more details about the limits you're hitting.

响应中包含的费率限制标头(来自Imgur API文档):

Rate limit headers included in responses (from Imgur API docs):

  • X-RateLimit-UserLimit -可分配的总积分.
  • X-RateLimit-UserRemaining -可用的总积分.
  • X-RateLimit-UserReset -何时重置信用的时间戳记(unix epoch).
  • X-RateLimit-ClientLimit -一天可以分配给该应用程序的总积分.
  • X-RateLimit-ClientRemaining -一天中该应用程序剩余的总积分.
  • X-RateLimit-UserLimit - Total credits that can be allocated.
  • X-RateLimit-UserRemaining - Total credits available.
  • X-RateLimit-UserReset - Timestamp (unix epoch) for when the credits will be reset.
  • X-RateLimit-ClientLimit - Total credits that can be allocated for the application in a day.
  • X-RateLimit-ClientRemaining - Total credits remaining for the application in a day.

这篇关于Imgur API-获取“太多请求"错误,即使"X-Ratelimit-Userremaining"不为0的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆