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
Retry-After handling does not honor --retry-max-time #7675
Labels
Comments
|
Did you try it? I already used |
I didn't try it because your issue here was incorrect. Now you've clarified it with more details. |
bagder
added a commit
that referenced
this issue
Sep 6, 2021
If Retry-After: specifies a period that is longer than what fits within --retry-max-time, then stop retrying immediately. Added test 366 to verify. Reported-by: Kari Pahula Fixes #7675
bagder
added a commit
that referenced
this issue
Sep 6, 2021
If Retry-After: specifies a period that is longer than what fits within --retry-max-time, then stop retrying immediately. Added test 366 to verify. Reported-by: Kari Pahula Fixes #7675
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I did this
I made this nginx config to test this out:
My command:
I expected the following
The command to fail within five seconds, not within 3 days. If the
Retry-After
time is aftermax-time
's limit, it should fail immediately.curl/libcurl version
Not the newest version but I saw no mentions of
max-time
orRetry-After
in the changelog.operating system
The text was updated successfully, but these errors were encountered: