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
Suppose this counts as a feature request, but I've observed that the API response doesn't include the rate limiting headers in not found/404 scenarios, and was curious if it would be feasible to include those response headers (x-ratelimit-limit, x-ratelimit-remaining) in the 404 scenarios as well?
The 404 request definitely counts against the rate limit, and the absence of the headers is consistent regardless of whether the request is authenticated with the api_key query param.
Thanks in advance for your consideration (and the Libraries.io service!), and please let me know if more information is required and/or any of the above is unclear.
The text was updated successfully, but these errors were encountered:
Suppose this counts as a feature request, but I've observed that the API response doesn't include the rate limiting headers in not found/404 scenarios, and was curious if it would be feasible to include those response headers (
x-ratelimit-limit
,x-ratelimit-remaining
) in the 404 scenarios as well?e.g. compare
with
The 404 request definitely counts against the rate limit, and the absence of the headers is consistent regardless of whether the request is authenticated with the
api_key
query param.Thanks in advance for your consideration (and the Libraries.io service!), and please let me know if more information is required and/or any of the above is unclear.
The text was updated successfully, but these errors were encountered: