RedirectManager: Document limitation of txt file export for dispatcher

[kwin]

The txt file export described in https://adobe-consulting-services.github.io/acs-aem-commons/features/redirect-manager/subpages/rewritemap.html should be clarified in terms of

• which values are contained in each line (https://httpd.apache.org/docs/current/rewrite/rewritemap.html#txt is very agnostic
• how is Sling mapping being performed to the 2nd argument per line when it contains backreferences?
• how is Sling mapping being performed to the 1st argument (if at all)
• to which degree regular expressions ar being supported (as mod_rewrite uses PCRE as outlined in https://httpd.apache.org/docs/current/rewrite/intro.html#regex), this supports things like %{VARNAME} as well.

I would assume that there are certain edge cases which lead to incorrect redirects (when being performed in Apache HTTPD).

Also it is not exactly clear what it is matched against (as the Sling URL decomposition cannot be performed by Apache: https://sling.apache.org/documentation/the-sling-engine/url-decomposition.html)

[kwin]

Seems that no mapping is applied at all (

acs-aem-commons/bundle/src/main/java/com/adobe/acs/commons/redirects/servlets/RewriteMapServlet.java

Line 93 in 575647b

out.printf("%s %s\n", source.trim(), target.trim());

) and the 1st argument simply being the source path and the 2nd argument being the target path (as maintained in the dialog without any additional post-processing).

[YegorKozlov]

Seems that no mapping is applied at all (

Yep. RewriteMapServlet was a quick implementation to pair Redirect Manager with pipeline-free redirects, and it simply dumps the rules in a two-column format. I don't mind supporting mapping and backreferences though.

Perhaps, we can control it by a selector. Mapping can be on by default and suppressed by .nomapping.txt .

[kwin]

One other limitation apart from mapping seems to be that the context prefix is neither considered for source nor target within the RewriteMapServlet.