SwitchUpCB

In addition, please add how we determine which requests route to a bucket. The documentation states: > Per-route rate limits exist for many individual endpoints, and may include the HTTP...

@devsnek confirmed https://github.com/discord/discord-api-docs/issues/5161 as a bug. Does this issue also contain a bug? The endpoint used in this scenario is `GetCurrentBotApplicationInformation`.

> In addition, please add how we determine which requests route to a bucket.  Based on this response from @advaith1 : > What does may include the HTTP method...

> Why did the request get rate limited? In the following partial log _(with a 1.01s wait time)_, we can see that the main issue occurs due to sending requests...

The date header is formatted in the RFC 1123 Time Format. ``` Fri, 08 Jul 2022 10:26:16 GMT ```

[This log](https://github.com/switchupcb/disgo/pull/14#issuecomment-1179433311) corresponds with the previous commit and showcases how global rate limit buckets either: 1. Do not expire at the second despite being presented at the second (i.e Fri,...

> I don't think I understand the issue here. > — @Bluenix2 Information surrounding **global rate limit handling** is too ambiguous for a straightforward implementation. > It is just stated...

https://github.com/switchupcb/disgo/pull/14#issuecomment-1179632428 confirms the (possible) behavior of the global rate limit algorithm with a **working global rate limiter implementation**. > The following log corresponds with the previous commit and updates the...

> I suppose you can consider this issue reproduced by me. > — @Bluenix2 Thanks for confirming! > Generally speaking though, some libraries only handle this issue after Discord tells...

> This is partially Discord's fault, yes, but not all the blame can be put on Discord. There are routes which do not produce ratelimit headers from what I remember,...