The system automatically includes the requested URI path in redirections. This appears to be always active without an option to disable it.

Problem:

• I have a redirect set up: domain.com/hello → mydomain.com/hello

• When users visit non-existent URLs like domain.com/hello/extra, they get automatically redirected to 404 redirect

• This creates broken redirects because the additional path segments (/extra) don’t exist on the target domain either

Requested Solution:

Please add an option to disable the automatic URI path inclusion, so administrators can choose between:

1. Include URI path (current default behavior): domain.com/hello/extra → domain.com/hello/extra

2. Exclude URI path (requested option): domain.com/hello/extra → domain.com/hello

Use Case:

This is essential for short URL services and fallback redirects where you want to ensure users always land on valid, existing pages rather than potentially broken URLs with appended paths.

Expected Outcome:

Users visiting domain.com/hello/extra should be redirected to domain.com/hello (base URL only), not to domain.com/hello/extra (which may not exist).

Currently, there’s no way to achieve this behavior since the URI path inclusion appears to be hardcoded as always active.