You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some APIs that support conditional requests, like the GitHub API, do not count it against your rate limit if you make a conditional request and get a 304 Not Modified response. It might be convenient to add an option to not apply client-side rate-limiting for 304s.
The text was updated successfully, but these errors were encountered:
JWCook
changed the title
Optionally handle 304 responses?
Handle 304 responses?
Sep 5, 2021
Similar to handling 429 responses (#4) and the limit_statuses option (#34), it also might be useful to provide a no_limit_statuses option to specify additional status codes that don't count against the rate limit.
I'll wait until there's an actual use case for that before implementing, though.
JWCook
changed the title
Handle 304 responses?
Handle 304 responses
Jan 10, 2023
Some APIs that support conditional requests, like the GitHub API, do not count it against your rate limit if you make a conditional request and get a
304 Not Modified
response. It might be convenient to add an option to not apply client-side rate-limiting for 304s.The text was updated successfully, but these errors were encountered: