Skip to content

Conversation

@cheesycod
Copy link

@cheesycod cheesycod commented May 2, 2024

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)

Copy link
Owner

@germanoeich germanoeich left a 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

cheesycod and others added 5 commits June 25, 2024 18:43
Apply suffix change

Co-authored-by: Germano Eichenberg <germanoeich@gmail.com>
Co-authored-by: Germano Eichenberg <germanoeich@gmail.com>
This also includes endpoint rewrites which is useful for the use case of custom gateway endpoints
@cheesycod cheesycod changed the title Request caching + add ratelimit-over-408 support Request caching + add ratelimit-over-408 + endpoint rewrite support Jun 25, 2024
@cheesycod
Copy link
Author

@germanoeich Tried resolving the changes

@cheesycod cheesycod requested a review from germanoeich June 25, 2024 13:55
cheesycod and others added 2 commits June 29, 2024 10:11
Co-authored-by: Germano Eichenberg <germanoeich@gmail.com>
Co-authored-by: Germano Eichenberg <germanoeich@gmail.com>
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

Successfully merging this pull request may close these issues.

4 participants