-
Notifications
You must be signed in to change notification settings - Fork 609
Regarding the behavior of Redirect Manager #3718
Description
Version:
AEMaaCS : 2026.2.24678.20260226T154829Z
ACS AEM Commons : 6.15.0
Reproduction steps (example)
- Create more than 1,000 redirect rules using Redirect Manager
→ shared-0 and shared-1 nodes are created under /conf/.../settings/redirects. - After that, upload a CSV that contains only a small number of rules (for example, 5 rules) and import it with the “Replace” option enabled.
- Expected behavior: The previous 1,000+ rules are deleted and only the 5 new rules remain.
- Actual behavior: The old rule nodes under the shared-* buckets remain, and the previous rules continue to be displayed in the UI.
I understand that the “Replace” option in Redirect Manager (the checkbox that is only visible on AEM as a Cloud Service) is intended to delete all existing rules under the specified path and replace them so that only the newly imported definitions remain.
Is it correct to assume that, due to the internal node structure being used (bucket nodes such as shared-0, shared-1, etc.), the delete operation on replace does not fully cover those bucket nodes and therefore does not remove all existing rules as intended?
Even when I run “Replace” to go from a state with more than 1,000 rules down to just 5 rules, the old rule nodes under the bucket nodes are not deleted and remain in the repository.
In other words, the previous large set of rules still appears in the UI.
Is this understanding of the behavior correct?
Any help would be appreciated.
Best regards,