(1) On the http response headers given to the client, the Retry-After: xxx field does not appear to be respected by the kaggle api.
(2) Additionally, it would be fantastic if more verbose logging is added w.r.t. rate limiting in general, so that api consumers can work within the allowed constraints.
Regarding (2) I have seen in the closed issues that kaggle api does not want to share the wait times. Consumers would really appreciate (2) if possible. But regarding (1), please can you fix Retry-After to reflect the actual wait time, or remove it so consumers don't build incorrect retry logic around it.
Related discussion:
Specifically: #132 (comment)
(1) On the http response headers given to the client, the
Retry-After: xxxfield does not appear to be respected by the kaggle api.(2) Additionally, it would be fantastic if more verbose logging is added w.r.t. rate limiting in general, so that api consumers can work within the allowed constraints.
Regarding (2) I have seen in the closed issues that kaggle api does not want to share the wait times. Consumers would really appreciate (2) if possible. But regarding (1), please can you fix Retry-After to reflect the actual wait time, or remove it so consumers don't build incorrect retry logic around it.
Related discussion:
CompetitionApiService/DownloadDataFiles#931Specifically: #132 (comment)