Skip to content

Respecting Retry-After headers #5864

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
namedgraph opened this issue Feb 13, 2025 · 0 comments
Open

Respecting Retry-After headers #5864

namedgraph opened this issue Feb 13, 2025 · 0 comments

Comments

@namedgraph
Copy link

namedgraph commented Feb 13, 2025

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant