You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
Currently, Envoy's local rate limit filter applies limits uniformly across all HTTP methods for a given route or virtual host.
However, while playing around with this feature internally we realized that different HTTP verbs may require different rate limiting policies. For example:
GET requests might be allowed at a higher rate than POST requests
PUT and DELETE requests might need stricter rate limiting than GET requests
Some verbs might not require rate limiting at all
It would be great if the existing local rate limiter is enhanced to set some per-verb limits, with this enhancement we could provide users with more fine-grained control over their traffic management.
Do you feel this is something that makes sense and that is feasible?
The text was updated successfully, but these errors were encountered:
Thank you a lot @wbpcode
I did not know about the descriptors. I think I can handle the usecase with that.
I close this feature request as it is not needed
Title: Add per-verb local rate limiter
Description:
Currently, Envoy's local rate limit filter applies limits uniformly across all HTTP methods for a given route or virtual host.
However, while playing around with this feature internally we realized that different HTTP verbs may require different rate limiting policies. For example:
GET requests might be allowed at a higher rate than POST requests
PUT and DELETE requests might need stricter rate limiting than GET requests
Some verbs might not require rate limiting at all
It would be great if the existing local rate limiter is enhanced to set some per-verb limits, with this enhancement we could provide users with more fine-grained control over their traffic management.
Do you feel this is something that makes sense and that is feasible?
The text was updated successfully, but these errors were encountered: