Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Correctly handle Retry-After header with 503 Service Unavailable #10

Open
austind opened this issue Aug 13, 2024 · 0 comments
Open

Correctly handle Retry-After header with 503 Service Unavailable #10

austind opened this issue Aug 13, 2024 · 0 comments
Assignees
@austind

Comments

@austind
Copy link
Owner

austind commented Aug 13, 2024

Currently, retryhttp makes the false assumption that any response that contains a Retry-After header must have been rate limited. In fact, Retry-After indicates planned downtime when accompanied by 530 Service Unavailable.

See MDN docs on Retry-After for details.
@austind austind self-assigned this Aug 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@austind austind

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@austind