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.

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

No support for rate-limit errors with retry-after headers. #174

Open
axiserik opened this issue Sep 27, 2021 · 0 comments
Open

No support for rate-limit errors with retry-after headers. #174

axiserik opened this issue Sep 27, 2021 · 0 comments

Comments

@axiserik
Copy link

When receiving errors for creating/updating objects/containers the headers are thrown away, this makes it impossible to respect retry-after headers which can be present in e.g. http 503 Service Unavailable or 429 Too many requests. (Unless Ḯm missing something obvious?)
A possible non breaking solution would be to add an optional field "Headers" to swift.Error and append headers to this error.
Another solution which would be breaking could be to simply return both error and headers from ObjectUpdate etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant