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

Support for X-RateLimit-* and X-Rate-Limit-* headers #77

Open
AdalynBlack opened this issue Sep 26, 2024 · 0 comments
Open

Support for X-RateLimit-* and X-Rate-Limit-* headers #77

AdalynBlack opened this issue Sep 26, 2024 · 0 comments

Comments

@AdalynBlack
Copy link

While these headers aren't necessarily standardized, many APIs return X-RateLimit-*, and some also return X-Rate-Limit-* headers. Most commonly, there's Limit, Remaining, and Reset headers, with Scope also being somewhat common (denoting that multiple rate limits are in use depending on the endpoint, as well as which rate limit is current being reported on). It would make sense to implement these headers to automatically set the rate limiter's internal values, that way the rate limiter and the API endpoint are synchronized in their expectations of when things should happen

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

1 participant