It is difficult to manage vanity redirects through PageBuilder resolvers because the regular expression for a resolver is case sensitive.
So /award/ works but /Award/ and /AWARD/ do not match unless we add each to the resolver.
Edge redirects were easy to setup as case insensitive.
Please consider adding a way to make the regex case insensitive. All regex parsers support some option for this.
John Flaherty
Hi, thanks for this suggestion. At present, Arc and PageBuilder don't make any assumptions about the case-sensitivity of URLs in the system, and so we require users to specify differently cased paths as different resolvers intentionally. However, I can understand the use case where certain organizations may want to be opinionated about the cases of their URLs and assume all variants are the same URL. Would this also mean that the content you're fetching in Content API should be case-insensitive, or would your code bundle know to transform the content's URL appropriately before querying Content API?
I think this is a reasonable suggestion, but I'd like to know how this would fit in with fetching from Content API before we move further.