#86944Add an optional regex target to sys_redirects
Description
We need an optional regex target. This target should resolve the source with the target regex rules.
Reviews 1
Files 1
History 68
-
Christoph Kratz changed tracker
BugFeature <span data-processor="relativetime" data-value="2018-11-17T10:41:51+00:00" > 11/17/18, 10:41 </span> -
Christoph Kratz changed is private <span data-processor="relativetime" data-value="2018-11-17T17:03:16+00:00" > 11/17/18, 17:03 </span>
-
Gerrit Code Review pushed patch set 1 for master to change 58919 status
NewUnder Review <span data-processor="relativetime" data-value="2018-11-20T16:34:32+00:00" > 11/20/18, 16:34 </span> -
Gerrit Code Review pushed patch set 2 for master to change 58919 <span data-processor="relativetime" data-value="2018-11-21T09:48:29+00:00" > 11/21/18, 09:48 </span>
-
Benni Mack changed is private <span data-processor="relativetime" data-value="2024-06-20T10:33:49+00:00" > 06/20/24, 10:33 </span>
-
Garvin Hicking changed category <span data-processor="relativetime" data-value="2024-06-20T12:54:04+00:00" > 06/20/24, 12:54 </span>
-
Benni Mack changed status
Under ReviewNew <span data-processor="relativetime" data-value="2026-11-09T11:23:50+00:00" > 11/09/26, 11:23 </span> -
Georg Ringer commented and changed status
NewClosed <span data-processor="relativetime" data-value="2026-11-12T19:20:47+00:00" > 11/12/26, 19:20 </span>
Closing this one as won’t do.
Regular expression redirects already support capture groups in the target (“$1”, “$2”, …), which covers the common case of carrying parts of the source over into the target. A dedicated regex target (pattern + replacement) would add a second regex layer with its own validation, UI and unsafe-expression handling, for what is a rare edge case. More specific needs can be implemented in an extension, for example with a custom PSR-15 middleware or the PSR-14 events of EXT:redirects.