Defines the set of simple URL rewrites for this prefix
Simple rewrites require no processing logic to handle the redirect and
the redirect is always processed before anything validity checks happen
Some examples:
/myprefix/item/{id} => /my-item/{id}
/myprefix/{year}/{month}/{day} => /myprefix/?date={year}-{month}-{day}
incomingURL is the URL template pattern to match including the /prefix using {name} to indicate variables
Example: /{prefix}/{thing}/site/{siteId} will match the following URL:
/myprefix/123/site/456, the variables will be {prefix => myprefix, thing => 123, siteId => 456}
NOTE: all incoming URL templates must start with "/{prefix}" (
TemplateParseUtil.TEMPLATE_PREFIX)
outgoingURL is the URL template pattern to fill with values from the incoming pattern,
this can start with anything, but will be processed as an external redirect if it starts with "http" or "/"
(unless it starts with "/{prefix}"), otherwise it will be processed as an internal forward
NOTE: the special variables which are available to all outgoing URLs from the system are:
{prefix} = the entity prefix
{extension} = the extension if one is available or '' if none
{dot-extension} = the extension with a '.' prepended if one is set or '' if no extension
{query-string} = the query string (e.g auto=true) or '' if none
{question-query-string} = the query string with a '?' prepended (e.g ?auto=true) or '' if none