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.

Sign up for GitHub

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

Jump to bottom

Route for checking rate/quota limits #27

Closed
alexwhitman opened this issue Dec 10, 2014 · 4 comments
Closed

Route for checking rate/quota limits #27

alexwhitman opened this issue Dec 10, 2014 · 4 comments
Assignees
@lonelycode
Labels
enhancement

Comments

@alexwhitman
Copy link
Contributor

It would be useful if there was a route for checking rate/quota limits without incurring a hit on those limits, similar to https://developer.github.com/v3/rate_limit/
@lonelycode lonelycode self-assigned this Dec 10, 2014
@lonelycode
Copy link
Member

Excellent idea. Marked as enhancement and adopted.

@alexwhitman
Copy link
Contributor Author

Also, might be worth adding rate limit data to response headers so extra requests aren't required to determine the remaining limits.

@lonelycode
Copy link
Member

Latest merge fixes this issue

Headers are added on responses, they may be slightly (-1) out of sync with the rate-check endpoint, but this is considered acceptable for now.

@lonelycode
Copy link
Member

This was buggy in dev, fixed now - you need to call /{api-listen-path}/tyk/rate-limits/ to get the data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lonelycode lonelycode

Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@alexwhitman @lonelycode