You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've asked on the mailing list but got no response, so I'm trying my luck here.
How does one go about respecting rate-limited 429 Too Many Requests responses with Jersey clients? Specifically making the client wait the period of time that was indicated in the Retry-After response header, before making the next request?
I imagine this requires some client-wide code because a request-scoped filter alone would not be able to deal with this.
I'm using the Jersey 3.1.0 client with ApacheConnectorProvider (Apache HTTP Client 4.5.13 I think).
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
I've asked on the mailing list but got no response, so I'm trying my luck here.
How does one go about respecting rate-limited
429 Too Many Requests
responses with Jersey clients? Specifically making the client wait the period of time that was indicated in theRetry-After
response header, before making the next request?I imagine this requires some client-wide code because a request-scoped filter alone would not be able to deal with this.
I'm using the Jersey 3.1.0 client with
ApacheConnectorProvider
(Apache HTTP Client 4.5.13 I think).The text was updated successfully, but these errors were encountered: