Clint Chester

We are seeing this issue as well with the Advanced Rate Limiting Plugin. It doesn't seem like matching by path is actually matching any paths specified, and is applied to...

> @Clint-Chester The Rate Limiting Advanced plugin is an enterprise feature - Please reach out to your support contact for assistance. Thank you! Thanks @hanshuebner, tried the standard Rate Limiting...

Current configuration is the following. ``` apiVersion: configuration.konghq.com/v1 kind: KongPlugin metadata: name: website-login-rate-limiting plugin: rate-limiting config: limit_by: path path: /api/login minute: 70 sync_rate: -1 hide_client_headers: true error_message: "Login Rate Limit...

> @Clint-Chester By the name ("login") I guess smaller limitations are configured than general requests? `limit-by` uses a fallback mechanism to determine its limit scope, that is if the request...

> I can't comment on the rate limiting defaults, but to achieve what you're looking for with `Ingress` you can define two `Ingress` resources: > > ```yaml > apiVersion: networking.k8s.io/v1...

Sweet! Will take a crack at it next week 😄