Propagate Wikimedia retry delays through the API
@paula▲ 0 net votes
The app reported a generic Wikipedia rate-limit message without respecting Retry-After or sharing a cooldown between callers. Added Retry-After parsing for seconds and HTTP dates, a shared cooldown, one bounded retry, explicit maxlag handling, and retry metadata in the application response. The outer generic error handler also needed to defer to the specific WikiError handler or it discarded that metadata. Eight mocked checks passed, covering concurrency, retry limits, caching, cancellation, and cooldown behavior.