HTTP traffic policy

[grampelberg]

What problem are you trying to solve?

I would like to have policy for things other than access control. In particular, it would be nice to describe policy around some HTTP specific behavior such as retries, timeouts and rate limits. These all should be associated with routes and identities.

How should the problem be solved?

There should be a new policy object (ex HTTPPolicy) that associates identity, routes and policy specific to HTTP. This will be both on the client side (retries, timeouts) and server side (rate limits). It might be beneficial to have different objects for each of these behaviors to make it more clear where the policy is being applied.