Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upHonor 429 HTTP Code / Retry-After header #3794
Comments
This comment has been minimized.
This comment has been minimized.
I reasonable suggestion methinks, even if that's a very rarely used response code and header... |
This comment has been minimized.
This comment has been minimized.
I think it is relatively common in *Something*-as-a-Service REST APIs.
I know that at least three we interact with (Infoblox, Okta, Workday) will
return it if we
exceed their transactions-per-time-period limits.
John
…On Fri, Apr 19, 2019 at 10:33 AM Daniel Stenberg ***@***.***> wrote:
I reasonable suggestion methinks, even if that's a very rarely used
response code and header...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#3794 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AFTWUXQWSO5H2L2QZ63RPETPRHQ4PANCNFSM4HHEKFXA>
.
|
This comment has been minimized.
This comment has been minimized.
I want to address this issue after #3804 has gone in, just to save me from having to do double work. |
This comment has been minimized.
This comment has been minimized.
At least one server written in Golang does sent this. It's used when it runs out of file descriptors. Another sensible use is in anything that runs in the cloud, hits a resource limit (clouds are made of rigid boxes), and cold-start times are known. |
This comment has been minimized.
This comment has been minimized.
It seems basically no browser supports it: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Retry-After#Browser_compatibility |
This comment has been minimized.
This comment has been minimized.
That fits with what I’ve seen, which is a Retry-After header on a HTTP 429 reply from HTTPS REST API servers.
I’ve not seen it on the kind of pages you would point a browser at.
John
John Hascall
IT Services
Iowa State Univ.
… On Aug 6, 2019, at 3:25 AM, Daniel Stenberg ***@***.***> wrote:
It seems basically no browser supports it:
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Retry-After#Browser_compatibility
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
This comment has been minimized.
This comment has been minimized.
Thanks, this looks really great. John
…On Wed, Aug 7, 2019 at 7:49 AM Daniel Stenberg ***@***.***> wrote:
Closed #3794 <#3794> via 640b973
<640b973>
.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#3794?email_source=notifications&email_token=AFTWUXQIUANWULQNNFPN33LQDLAEDA5CNFSM4HHEKFXKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOS5SIRKI#event-2539948201>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFTWUXSSETKHRV5FAPMT4K3QDLAEDANCNFSM4HHEKFXA>
.
|
This comment has been minimized.
This comment has been minimized.
Thanks @bagder - but when I now try to use this in 7.66.0 against for instance Zenodo API it seems curl is still fails early on |
This comment has been minimized.
This comment has been minimized.
Try for instance
|
The command line client's --retry option should recognize and honor the 429 HTTP status return and the accompanying 'Retry-After' header.
Affects all versions, but I happen to be running:
on: