Rate Limit by request method with policy

[GuyT2002]

Is your feature request related to a problem? Please describe.
When trying to rate limit with a policy, using the variable ${request_method} is rejected. Trying to use ${http_request_method} does not work either.

Describe the solution you'd like
Allowing the use of ${request_method} as a key for rate limiting.

Describe alternatives you've considered
Adding the key ${request_method} to the usable keys in rate limit policies.

[github-actions]

Hi @GuyT2002 thanks for reporting!

Be sure to check out the docs and the Contributing Guidelines while you wait for a human to take a look at this 🙂

Cheers!

[pdabelf5]

Hi @GuyT2002, thank you for creating an issue about this. I just wanted to clarify something about the requirements. Given using the request method would rate limit any user who makes, for example, a GET request. Is that your need? Or would the need be a combination of the client IP + request method? More context around your use case may help.

[GuyT2002]

Hi @pdabelf5 , My use case is solely about the request method, so if too many users send a GET (or POST) request within the time range, the are limited/

[pdabelf5]

Thanks for clarifying @GuyT2002, this issue will be discussed at our next triage call on the 6th May.

[GuyT2002]

Is there any update to this issue?

[vepatel]

Hi @GuyT2002 at this moment only keys listed in https://docs.nginx.com/nginx-ingress-controller/configuration/policy-resource/#ratelimit are supported, we are looking into expanding this further based on your requirement

[GuyT2002]

As I’ve stated, we’re trying to rate limit requests only via their HTTP method.