I have a rule in-place to block access to a particular pathname; the customer wants to display a specific blocking page instructing the user to use that function, they need to use the non-public interface on VPN.

Blocking the page returns a 403 which has a generic blocking page because so many other policies share the 403 response.

A Direct Route enables me to create that custom blocking page, but the pathname itself is mixed-case and appears in many variations, and so that Direct path will likely never match. Converting the path to Lower Case, for example, would enable this.