X-RateLimit-Reset and Retry-After Ratelimit headers

[ghost]

After hitting the ratelimit a few times through the ratelimit-compliant RequestBuffer in the Discord4J Java API, I visited the docs for ratelimits in search for an answer -- why was I hitting the ratelimit. I found @hydrabolt commenting about the use of X-RateLimit-Reset instead of Retry-After. (#108) As @night doesn't see a need to replace X-RateLimit-Reset with Retry-After, may I politely ask you guys to implement both headers please?

Edit 2: As @satom99 pointed out, although there is a Date header, it would be better to also include the Retry-After header, as recommended on RFC-6585

[satom99]

Someone, perhaps @night himself, pointed out the Date header. Which, being Discord's time UTC, may be used to get the exact time before the payload is generated - and thus do a simple subtraction.

[b1naryth1ef]

The Retry-After header still exists for ratelimited requests.