Closed Ankush-Chander closed 3 years ago
Hi @Ankush-Chander
It seems to be a bug in their API, they are moving to their new version, but this new version should not break compatibility with the previous version.
https://github.com/CrossRef/rest-api-doc#rate-limits
I will include a default value in case of exception.
Hello @ppolischuk
We noticed an error in the library that is related to the value being retrieved in the header of the Crossref API. It seems the attributes X-Rate-Limit-Limit and X-Rate-Limit-Interval changed their behavior.
Previously:
X-Rate-Limit-Limit: 50 X-Rate-Limit-Interval: 1s
Now:
X-Rate-Limit-Limit: 50, 50 X-Rate-Limit-Interval: 1s, 1s
Is there any reason for this change?
Related Issue in Crossref API repository : https://gitlab.com/crossref/issues/-/issues/1389
Hi @Ankush-Chander;
I have just pushed the workaround to master, can you check if it is working.
Thanks @fabiobatalha Workaround works as expected. I am keeping the issue open till we hear from our friends at crossref.
Hi @fabiobatalha,
It seems like crossref api has made some modifications in header format.
'x-rate-limit-limit': '50, 50', 'x-rate-limit-interval': '1s, 1s',
Running below code
is giving following error: