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
Currently, the domain matchers (e.g., used in route_upstream) support only child_match and exact_match. However, there’s no support for wildcard matching. For example, something like:
The exact syntax or feature set isn’t particularly important to me—what matters more is having the capability to perform wildcard-based filtering, especially in cases where exact_match or child_match aren’t sufficient.
I understand that wildcard matching may be slower by nature, but I still believe it could be quite useful for certain edge cases.
The text was updated successfully, but these errors were encountered:
At the moment, I’m unfortunately swamped. If you haven’t had a chance to get to it by the time I need it, I’ll definitely take care of it myself.
That said, could you elaborate a bit more on how exactly you envision this? Your proposal still leaves quite a bit of room for interpretation, and I’d like to make sure we’re aligned before moving forward.
The wildcard_match code would be much like the child_match code, the difference is:
child_match insert example.net as net.example. to a Trie<String, ArcEscaper>,
wildcard_match insert a*.example.net as net.example.a to a Trie<String, ArcEscaper>.
*.example.net seems to be a special case as it should match both example.net and a.example.net.
Currently, the domain matchers (e.g., used in
route_upstream
) support onlychild_match
andexact_match
. However, there’s no support for wildcard matching. For example, something like:would ideally match:
The exact syntax or feature set isn’t particularly important to me—what matters more is having the capability to perform wildcard-based filtering, especially in cases where
exact_match
orchild_match
aren’t sufficient.I understand that wildcard matching may be slower by nature, but I still believe it could be quite useful for certain edge cases.
The text was updated successfully, but these errors were encountered: