OpenAPITools / OpenAPITools/openapi-generator
[REQ] automatically retry of all http operations on http 429 with retry-after header
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 26.8k
- Forks
- 7.7k
- PR merge metrics
- PR metrics pending
Description
Is your feature request related to a problem? Please describe.
Our server implement an API limiter with status code 429 and the retry-after header. Currently we have to catch the response outsite of the generated client and retry from applicaition level
https://datatracker.ietf.org/doc/html/rfc6585#section-4
Describe the solution you'd like
Would be good if the generated code automatically retry the call after the provided time in the retry-after header like it is does on timeouts
Describe alternatives you've considered
implement the retry logic outsite of the generated client code or patching the generated code
Additional context
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the generated-client timeout retry behavior with handling for HTTP 429 responses and the Retry-After header, using RFC 6585 section 4 as the protocol reference. Done means generated clients automatically retry all HTTP operations after the server-provided delay, without application-level retry logic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, openapi
- Domain
- api, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100