You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The text was updated successfully, but these errors were encountered:
YegorKozlov
changed the title
Redirect Manager:
Redirect Manager: support handling redirects when the request path does not start with /content
May 17, 2023
YegorKozlov
added a commit
to YegorKozlov/acs-aem-commons
that referenced
this issue
May 17, 2023
* #3105 Redirect Manager: support handling redirects when the request path does not start with /content
* #3138 fix errors when re-ordering redirects in touch ui
* #3150 Support for case-insensitive redirect rules
Required Information
Expected Behavior
Redirect manager should support handling redirects when the request path does not start with /content, .e.g.
http://localhost:4503/test
Actual Behavior
by default the Redirect Filter listens to /content/* requests:
![image](https://private-user-images.githubusercontent.com/2543854/238885435-96f8aa02-f5fa-44f0-93ce-efb2d70adfad.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkxNjUyMTksIm5iZiI6MTczOTE2NDkxOSwicGF0aCI6Ii8yNTQzODU0LzIzODg4NTQzNS05NmY4YWEwMi1mNWZhLTQ0ZjAtOTNjZS1lZmIyZDcwYWRmYWQucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDIxMCUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTAyMTBUMDUyMTU5WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9ZmQxMjY0ZWFhZjNmYThlNDRhZDk3YjQzNjE3ZjIyM2U0NjU1OTVmZDQwNzYxYzg3ODZmODcxMWYzZjUzNTJiYiZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.53HDPpZu-JJyyJlXaWBxPCauGrZUA__b5GPI-Ahsn5o)
there can be scenarios when one would want to handle redirects on the root level, however, setting the paths property to "/" has not effect.
Links
Links to related assets, e.g. content packages containing test components
The text was updated successfully, but these errors were encountered: