Neue Rate-Limiting-Header für die API
Die Cloudflare-API liefert jetzt standardisierte Rate-Limiting-Header, und die neuesten SDKs weichen automatisch bei erreichten Limits aus.
Cloudflare's API now supports rate limiting headers using the pattern developed by the IETF draft on rate limiting ↗︎. This allows API consumers to know how many more calls are left until the rate limit is reached, as well as how long you will need to wait until more capacity is available.
Our SDKs automatically work with these new headers, backing off when rate limits are approached. There is no action required for users of the latest Cloudflare SDKs to take advantage of this.
As always, if you need any help with rate limits, please contact Support.
Changes
New Headers
Headers that are always returned:
Ratelimit: List of service limit items, composed of the limit name, the remaining quota (r) and the time next window resets (t). For example:"default";r=50;t=30Ratelimit-Policy: List of quota policy items, composed of the policy name, the total quota (q) and the time window the quota applies to (w). For example:"burst";q=100;w=60
Returned only when a rate limit has been reached (error code: 429):
- Retry-After: Number of Seconds until more capacity is available, rounded up
SDK Back offs
- All of Cloudflare's latest SDKs will automatically respond to the headers, instituting a backoff when limits are approached.
GraphQL and Edge APIs
…