-
-
Notifications
You must be signed in to change notification settings - Fork 7.5k
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
Add retry with exponential backoff for GetRemote for 429 and other temporary HTTP errors #11312
Comments
bep
changed the title
GetRemote support for rate limits
Add retry with exponential backoff for GetRemote for 429 and other temporary HTTP errors
Jul 31, 2023
bep
added a commit
to bep/hugo
that referenced
this issue
Aug 3, 2023
…ry HTTP errors Fixes gohugoio#11312
bep
added a commit
to bep/hugo
that referenced
this issue
Aug 3, 2023
…ry HTTP errors Fixes gohugoio#11312
bep
added a commit
to bep/hugo
that referenced
this issue
Aug 4, 2023
…ry HTTP errors Fixes gohugoio#11312
bep
added a commit
to bep/hugo
that referenced
this issue
Aug 4, 2023
bep
added a commit
to bep/hugo
that referenced
this issue
Aug 4, 2023
bep
added a commit
that referenced
this issue
Aug 4, 2023
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We have a hugo site that is making a number of GetRemote calls to an authenticated api. We hit a point where we are receiving
429 Too Many Requests
errors due to the requests per second rate limit etc.As most apis will have some form of rate limits this is a proposal to include some solution/strategy for it. Perhaps some configurable limit to the requests per second of getremote? or some retry with exponential backoff?
The text was updated successfully, but these errors were encountered: