I have configured the rate limit plugin with limit_by IP in the AKS cluster and it working properly but it consider the preflights request(options) too. So we could not exactly met the rate limit policy in the Custer. Can you please let me know whether we can set the rate limit based on the response status code like 200 etc.
I have followed the below documentation to configure the rate limit in AKS.
Thanks for your update.
I have created the 2 routes with following method attribute.
r1 method [POST,GET]
r2 method [OPTIONS]
and apply the rate limit plugin to r1 and it working as expected. (Rate-Limit value won’t applied to the OPTIONS request)
After reaching the rate-limit for the r1 route path and it failed with CROS origin error instead of returning rate-limit error message i.e { “message”: “API rate limit exceeded” } with status code 429.
Please let me know if i missed anything else from my side
Thanks for your update.
I have created the 2 routes with following method attribute.
r1 method [POST,GET]
r2 method [OPTIONS]
and apply the rate limit plugin to r1 and it working as expected. (Rate-Limit value won’t applied to the OPTIONS request)
After reaching the rate-limit for the r1 route path and it failed with CROS origin error instead of returning rate-limit error message i.e { “message”: “API rate limit exceeded” } with status code 429.
Please let me know if i missed anything else from my side