Feature #93288
Updated by Sybille Peters about 3 years ago
h2. Update _Oct 16, 2021_ Since behaviour has now been changed to use a page link as target (e.g. t3://page?uid=123) and not a path, redirect chains should no longer be created by automatic redirect creation. They might however still be created manually and there is the question of the older redirects already existing. h2. Clarification of terms *Clarification* : I am talking about *redirect chains* here, not *redirect loops*. *chain* : example: * /a => /b, /b => /c * /a => /b, /b => /c, /c => /d 2 (or more) redirects have to be followed now for redirecting to the final page. If one of the redirects is removed, the chain breaks *loop* : example * /a => /a * /a => /b, /b => /a ---- h2. Description If slugs URLs are changed several times, redirect chains -are- used to be created by automatic redirect creation, are created, e.g. /a -> /b -> /c. If these are merged, it reduces the number of requests necessary to load a page. Could be done on-the-fly or as a command. *Before* : <pre> /a -> /b /b -> /c </pre> *After* <pre> /a -> /c /b -> /c </pre> NEW: The behaviour has now been changed to use page links as targets, so the result would now be: <pre> /a -> t3://page?uid=111 /b -> t3://page?uid=111 </pre>