Issue Feature Closed

#86944Add an optional regex target to sys_redirects

Christoph Kratz 11/16/18, 15:46 updated 11/12/26, 19:20

Description

We need an optional regex target. This target should resolve the source with the target regex rules.

Reviews 1

Files 1

History 68

  1. Christoph Kratz changed tracker Bug Feature 11/17/18, 10:41

  2. Christoph Kratz changed is private 11/17/18, 17:03

  3. Gerrit Code Review pushed patch set 1 for master to change 58919 status New Under Review 11/20/18, 16:34

  4. Gerrit Code Review pushed patch set 2 for master to change 58919 11/21/18, 09:48

  5. Benni Mack changed is private 06/20/24, 10:33

  6. Garvin Hicking changed category 06/20/24, 12:54

  7. Benni Mack changed status Under Review New 11/09/26, 11:23

  8. Georg Ringer commented and changed status New Closed 11/12/26, 19:20

    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.