Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
Re: working around status code 429
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Ray Satiro via curl-users <curl-users_at_lists.haxx.se>
Date: Wed, 7 Feb 2024 14:22:43 -0500
On 2/1/2024 4:17 AM, Dirk Hünniger via curl-users wrote:
> you are right. Its retrying after one second, and not doing the
> exponential fallback it usually does. Thats why it concluded after a
> few minutes. Thanks for the explanation that curl is following the
> servers proposal to try again after one second. Everything is
> explained this way. If you want, you can add a command line option to
> override the servers proposal. For me it is not needed because, I do
> the retrying in an external loop around the call to curl now.
We've fixed the issue by ignoring Retry-After time when it is shorter
than curl's retry time. [1]
[1]: https://github.com/curl/curl/commit/924e264b
Date: Wed, 7 Feb 2024 14:22:43 -0500
On 2/1/2024 4:17 AM, Dirk Hünniger via curl-users wrote:
> you are right. Its retrying after one second, and not doing the
> exponential fallback it usually does. Thats why it concluded after a
> few minutes. Thanks for the explanation that curl is following the
> servers proposal to try again after one second. Everything is
> explained this way. If you want, you can add a command line option to
> override the servers proposal. For me it is not needed because, I do
> the retrying in an external loop around the call to curl now.
We've fixed the issue by ignoring Retry-After time when it is shorter
than curl's retry time. [1]
[1]: https://github.com/curl/curl/commit/924e264b
-- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-users Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2024-02-07