Feature #93288
Merge redirect chains
Status:
New
Priority:
Should have
Assignee:
-
Category:
Link Handling, Site Handling & Routing
Target version:
-
Start date:
2021-01-14
Due date:
% Done:
0%
Estimated time:
PHP Version:
Tags:
redirects,redirect chains,cleanup redirects
Complexity:
Sprint Focus:
Description
Clarification : I am talking about redirect chains (redirects to other URL) here, not redirect loops (redirects to same URL).
If URLs are changed several times, redirect chains 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 :
/a -> /b
/b -> /c
After
/a -> /c
/b -> /c
This way, /a and /b are still redirected, but /a redirects directly to /c instead of to /b and then to /c.
Related issues
Updated by Sybille Peters 7 months ago
- Related to Task #89301: Streamline automatic slug & redirects handling added
Updated by Sybille Peters 7 months ago
- Related to Bug #93287: Avoid creation of unnecessary redirects on Slug changes added
Updated by David Bruchmann 6 months ago
- Related to Bug #92748: Infinite redirects (redirect loop) when updating slugs added
Updated by Sybille Peters 4 months ago
- Related to Bug #89327: Auto redirect: Could not resolve target page added
Updated by Sybille Peters 3 months ago
If not the path, but the page id (or t3://page?id=ID) is used as target, this would no longer be a problem. See #89327