Susan or Brian, would you describe more about these use cases? a). * in the middle - "foo.*.com" b). multiple * - "*.bar.*.com"
Why it's required or how it's useful? I agree with we don't need to follow the wildcard certificats semantics (RFC6125 6.4.3) in the fqdn field if we want. However, I'm wondering why the left-most label wildcard is not enough. — Masaori On Tue, Jun 20, 2023 at 9:19 AM James Peach <jpe...@apache.org> wrote: > > > > > On 20 Jun 2023, at 8:19 am, Alan Carroll <a...@network-geographics.com> > > wrote: > > > > Note this could be done the same way as remap - put all the literals in one > > search structure and check for that first. If there's a match, it's for a > > specific line in the file and one need only linear search the regular > > expressions before that line. Anecdotally I've been told you can improve > > remap performance by expanding regular expressions into literals if the set > > of values isn't too large (e.g. "*.swoc.io" in practice means > > "zwoop.swoc.io", "susan.swoc.io" and "amc.swoc.io"). > > Yup there are various ways to redesign the feature to improve lookup > performance, but I expect they would all be breaking changes to existing > config. > > > -----Original Message----- > > From: James Peach <jpe...@apache.org> > > Sent: Monday, June 19, 2023 12:09 AM > > To: dev@trafficserver.apache.org > > Subject: Re: [Discussion/Proposal] Regex support in sni.yaml > > > > It’s not made explicit in the documentation, but it looks like the policy > > match depends on the order of entries, so you’d have to make a linear scan > > doing regex matches, which makes it more attractive to use regex matching > > to reduce the size of the list. >
