- Issue created by @jbiswas
The Redirect module currently disallows adding source redirects with trailing slashes (e.g., /example/). This limitation makes it challenging to manage frontend redirects where trailing slashes may need to be included. For headless or decoupled CMS setups, where Drupal acts purely as the content management backend and the frontend handles routing, the ability to add redirects with trailing slashes is necessary. This is a common use case for headless or backend-only CMS setups.
The current behavior in the Redirect module restricts users from creating source paths with trailing slashes, based on an earlier issue: "
Don't allow adding source paths with trailing slashes, they won't ever work →
". While this makes sense for sites where Drupal manages routing, it limits flexibility for backend-only setups and headless CMS configurations, where managing trailing slashes on source paths is essential for consistency .
Allow users to enter source paths with trailing slashes as valid redirects. This change would only affect configurations where Drupal is used as a backend or headless CMS, allowing developers the flexibility to manage paths in a way that matches frontend expectations.
Active
1.10
Code