Problem
Rate limiting rules are often needed for endpoints where part of the path is dynamic — for example, an ID segment that is not a UUID, or a service name that varies between environments.
Currently, wildcard matching (*) is only supported at the end of a descriptor value (e.g., /api/*). Patterns with
* in any other position were treated as literal strings, making it impossible to express rules like /api/*/action or svc*-prod without enumerating every possible value explicitly.
What we support
Wildcard matching is extended to support * at any position in a descriptor value — trailing, middle, or multiple occurrences. This allows rate limit rules to match dynamic path segments regardless of where they appear in the string, without requiring any additional configuration flags.
Existing trailing-only wildcard behavior is fully preserved.
Problem
Rate limiting rules are often needed for endpoints where part of the path is dynamic — for example, an ID segment that is not a UUID, or a service name that varies between environments.
Currently, wildcard matching (
*) is only supported at the end of a descriptor value (e.g.,/api/*). Patterns with*in any other position were treated as literal strings, making it impossible to express rules like/api/*/actionorsvc*-prodwithout enumerating every possible value explicitly.What we support
Wildcard matching is extended to support
*at any position in a descriptor value — trailing, middle, or multiple occurrences. This allows rate limit rules to match dynamic path segments regardless of where they appear in the string, without requiring any additional configuration flags.Existing trailing-only wildcard behavior is fully preserved.