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
Support for case-insensitive path prefix matching, e.g. with caseSensitive: false (naming not important to me, that's how it's called in xDS if you're using Envoy).
HttpRoute currently requires regular expressions to achieve case-insensitive path prefix matching.
Existing code may expect URLs to be case-insensitive, since file systems can be case-insensitive. Windows Servers are a good example. Also, case-insensitivity helps users who might enter a URL manually in their address bar.
We would also like to use replacePrefixMatch on a URLRewrite. This is explicitly disallowed for regular expressions, so we really need the case-insensitive support on prefix matches, specifically.
Regular expressions are still a less optimal solution regardless:
The specific Gateway implementation may not guarantee reasonable ordering, and there is no flag to denote the priority of a regex match. We have to rely on a specific implementation like Envoy Gateway ordering the regular expression routes sensibly, which is not guaranteed by the Gateway API itself. If they are mis-ordered, a less specific path match could apply first. This is a problem if a more root path has an authentication requirement, but a nested, more specific path is intentionally public (like is common if you have a /prefix/authenticate path that accepts credentials to authenticate in the first place).
Regular expressions could be less performant.
Feature parity with other API Gateway technologies (some required fields have be removed for brevity of examples):
Kong Gateway which uses Kubernetes Ingress API (doesn't have case-insensitive, but Kong has explicit regex priority for confidence the more nested, specific route is applied):
Thanks for filing this @gorban! If you have time to work on this in the next 2-3 months, do you mind proposing it in our v1.2 release scoping discussion?
What would you like to be added:
Support for case-insensitive path prefix matching, e.g. with
caseSensitive: false
(naming not important to me, that's how it's called in xDS if you're using Envoy).Why this is needed:
HttpRoute currently requires regular expressions to achieve case-insensitive path prefix matching.
replacePrefixMatch
on a URLRewrite. This is explicitly disallowed for regular expressions, so we really need the case-insensitive support on prefix matches, specifically./prefix/authenticate
path that accepts credentials to authenticate in the first place).ignoreUriCase
:From documentation:
The text was updated successfully, but these errors were encountered: