wireclient.ts and googledrive.ts don't honor Retry-After header in 429 and 503 responses
Opened this issue · 2 comments
I have experimentally determined that the wireclient does not pause when it receives a 429 Too Many Requests response with a Retry-After header. As wireclient.ts does not contain any references to 429, 503 or the retryAfterMs function in requests.ts, this appears to be an oversight in the code.
As googledrive.ts likewise contains no references to 429, 503 or the retryAfterMs function in requests.ts, but dropbox.ts does contain references to 429, 503 and the retryAfterMs function in requests.ts, presumably googledrive.ts shares this oversight, but dropbox.ts does not.
It's not an oversight, but there was simply never an RS server implementation that necessitated throttling for authorized requests. The logical explanation is that the function only exists for the Dropbox back-end.
Well, there is a native RS implementation that sends 429s now!
remotestorage/armadietto@00f3efd