feat: support retry-after header in retry middleware #639
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Let me know if there's any feedback you have on the proposed change - thanks! |
yordis
force-pushed
the
master
branch
6 times, most recently
from
2bca420 to
fe7207c
Compare
Adds :use_retry_after_header option to allow the client to align its retry strategy with server-side rate limiting
matt-brale-xyz
force-pushed
the
support-retry-after-header
branch
from
125e5af to
34d91d0
Compare
yordis
reviewed
Nov 22, 2024
matt-brale-xyz
commented
Nov 22, 2024
Replaces the dependency on date_time_parser with an HTTP-date parser implementation based on the one used in https://github.com/wojtekmach/req
|
🚀 💜 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds :use_retry_after_header option to allow the client to align its retry strategy with server-side rate limiting