Open aaccomazzi opened 6 years ago
It looks like we no longer report the correct remaining limits for queries via HTTP headers, e.g.
curl -v -H "Authorization: Bearer $ADS_DEV_KEY" 'https://api.adsabs.harvard.edu/v1/search/bigquery?q=star' < HTTP/1.1 200 OK < Date: Wed, 07 Feb 2018 21:35:15 GMT < Content-Type: application/json < Content-Length: 317 ... < X-RateLimit-Limit: 100 < X-RateLimit-Remaining: 100 < X-RateLimit-Reset: 1518039315
The rate limit is stuck at 100 no matter how many queries I make. The same is true for at least the query endpoint, as if the system
It looks like we no longer report the correct remaining limits for queries via HTTP headers, e.g.
The rate limit is stuck at 100 no matter how many queries I make. The same is true for at least the query endpoint, as if the system