Retry-After, the internet standard counterpart of x-ratelimit-reset, was for some reason always being set to the timeWindow property when rate limiting took place - so for instance even when a user had to wait for 5 more seconds for rate limiting to be lifted (with a timeWindow of 15 seconds), the user would still see on the header the number 15 instead of 5
I traced back a change that, while introducing the optional draft headers feature, had done away with this but probably couldn't change the default behavior to make it non-breaking
Retry-After, the internet standard counterpart ofx-ratelimit-reset, was for some reason always being set to thetimeWindowproperty when rate limiting took place - so for instance even when a user had to wait for 5 more seconds for rate limiting to be lifted (with a timeWindow of 15 seconds), the user would still see on the header the number 15 instead of 5I traced back a change that, while introducing the optional draft headers feature, had done away with this but probably couldn't change the default behavior to make it non-breaking
While another breaking PR is up, I think we can also make this change