redirect from path should allow smarter replacements

[jtmoon79]

problem

Given a path like https://service.corp.com/a/1234 I would like a shortcut path http://goto/a/1234 to redirect to https://service.corp.com/a/1234.
Currently, it cannot.

The user requested path /a/1234 does not match the Administrator-set redirect entry /a.

Allowing the user to declare redirects where the from path could be a bit smarter would be ideal.

idea 1

Allow strings-style Template Syntax in the from redirect path. Matching the request path would vary from current strictly string compare of requested from_path == redirect from_path to something smarter.

For example, redirects file entry like:

/a${path} https://service.corp.com/a${path} user

Request http://goto/a/1234 would redirect to https://service.corp.com/a/1234.
Request http://goto/a would redirect to https://service.corp.com/a.
In effect, all requested paths /a* would match.

Something difficult about this is allowing multiple similar redirect paths. For example, imagine redirects entrys

/a${path} https://service.corp.com/a${path} user
/alpha https://build-server.corp.com/builds/release-alpha/ user

All requests to http://goto/alpha would match to entry /a${path} (user would end up at unwanted location https://service.corp.com/alpha). The matching algorithm should allow matching these as the Administrator would expect:
/alpha -> https://build-server.corp.com/builds/release-alpha/
a/123 -> https://service.corp.com/a/123
Otherwise, a redirect entry like /a${path} "smothers" any further redirect entries that start with substring /a.

[jtmoon79]

Implemented via Required Request Modifiers and Template Syntax replacements.