Skip to content

Respecting Retry-After headers #5864

@namedgraph

Description

@namedgraph

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions