Extend the proxy to provide RateLimit headers about dev-proxy HOT 5 CLOSED

@waldekmastykarz yes! That's where my thoughts were going with this one.

from dev-proxy.

This would be a great addition to use the new functionality and help developers test how their application is backing off when it starts getting rate limiting information.

@gavinbarron what do you think would be the best way to implement this?

from dev-proxy.

@jansenbe thanks for that info on the rate limiting, that's going to be very helpful!
AFAIK the resource unit concept of rate limiting also applies to the SPO apis that are exposed via Graph and it's a scenario we would need to account for sooner or later.

On the implementation question, I think we need to sit down and look at how we can break apart the traffic handing to allow for some kind of middleware setup which might allow for a plug-in style of extension to the tool where a plug-in might define the rate limiting behavior.

This could allow for complex configuration via config for the middleware while still providing an option for some lightweight usage scenarios for primitive failures etc as we currently provide.

from dev-proxy.

@gavinbarron could the first implementation become a part of our behaviors work along with other service limits? In the long run we could allow for more flexibility through plugins. What do you think?

from dev-proxy.

Duplicate of #210. We'll close this issue and track work status using #210 which is linked to the PR

from dev-proxy.