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

Response should not be cachable if x-ratelimit-limit is set #29

Closed
avoidwork opened this issue Mar 30, 2015 · 0 comments
Closed

Response should not be cachable if x-ratelimit-limit is set #29

avoidwork opened this issue Mar 30, 2015 · 0 comments
Assignees
Labels

Comments

@avoidwork
Copy link
Owner

By generating an Etag, it's possible for a client to miss rate limiting headers.

@avoidwork avoidwork added the bug label Mar 30, 2015
@avoidwork avoidwork self-assigned this Mar 30, 2015
avoidwork added a commit that referenced this issue Mar 30, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant