Hello Community - I have a requirement to provide the user interface/utility to the authors to manage the redirects which will eventually be stored in etc/map config. I know that we have ACS Redirect Manager but the requirement is to build a custom one. Could someone provide some suggestions?
I think, the ACS Redirect Manager helps us to manage redirects at the Apache level, but I see that you are expecting to store redirect configurations at etc/map level, seems like you want to configure internal redirects.
If that is the case, then you need to write a custom logic
If the requirement is not storing under etc/map then you need to do analysis or do simple POC whether ACS redirect manager is meeting all your requirements or not, if not then you need to do reverse engineering.
Building your own custom one, I suggest you reverse engineer the ACS Redirect Manager, understand why did they decide to design this redirect manage. Then execute your own. (you should also try to set it up on your local publisher + dispatcher, see how it works).
I think their ACS Redirect Manager makes sense to me, as rules are coming from static files within the web server, the redirect rules take effect before reaching to the AEM publishers... you wouldn't want your publishers to be taking the load.