-
Notifications
You must be signed in to change notification settings - Fork 24
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
Request caching + add ratelimit-over-408 + endpoint rewrite support #13
base: main
Are you sure you want to change the base?
Conversation
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.
Thank you so much for the interest and contribution! I apologize for the delay reviewing this. There are some points of improvement but its all minor stuff, I like the changes and I think there is value in adding them to nirn :) Let me know if there are any questions about anything I've written here and let me know if these comments make sense to you aswell
Apply suffix change Co-authored-by: Germano Eichenberg <[email protected]>
Co-authored-by: Germano Eichenberg <[email protected]>
This also includes endpoint rewrites which is useful for the use case of custom gateway endpoints
Co-authored-by: Germano Eichenberg <[email protected]>
Not used by upstream
@germanoeich Tried resolving the changes |
Co-authored-by: Germano Eichenberg <[email protected]>
Co-authored-by: Germano Eichenberg <[email protected]>
This PR adds support for (primitive) request caching for certain routes as well as the ability to 429 instead of 408 on a context deadline exceeded error. It also adds endpoint rewrite support which is useful in the instance where you may want to rewrite discord requests to other paths (for example, where the simple wsProxy string is not enough or if you have a seperate service for capturing state, an endpoint rewrite can be used to ensure all bots use it)