-
Notifications
You must be signed in to change notification settings - Fork 189
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
feat: return Retry-After header in case of 429/Too Many Requests on thumbnail WebDAV endpoint #9240
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
c758cec
to
e003d29
Compare
…humbnail WebDAV endpoint
e003d29
to
dbb90e3
Compare
Quality Gate passedIssues Measures |
hm, yeah ... determining a retry after timeout is hard. 5min is pretty long ... I'd start with 30sec and use an exponential backoff. Also, the current Throttle limit is global ... maybe sth like https://github.com/go-chi/httprate with a limit on real ip and endpoint? urg but that requires common state, which is why there is https://github.com/go-chi/httprate-redis since this is something I expect to be tweakable ... should we just add an env var for this? |
But this is more for real rate limiting which could be used for some kind of far usage of the thumbnail service. Or am I miss-understanding your comment?
Two vars then? One for done and one for not done ....
I didn't want to over-engineer this tbh 🙈 |
Please finish or close 😄 |
I should have written "finish" 😬 |
@butonic wants it -> please finish |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you make it configurable?
Feel free to take over. Thx |
IMO we need this to tell clients to actually retry fetching thumbnails. |
This has been implemented in #10280 |
Description
#9199 (comment)
Related Issue
#9199 (comment)
Motivation and Context
#9199 (comment)
Types of changes
Checklist: