Sign in to Community
Sign in to view all badges
We are facing issue with /welcome.html in dispatcher!
/welcome is by default mapped to AEM welcome page i.e. /libs/cq/core/content/welcome.html
/welcome is also mapped (AEM resource mapping)to our project page i.e /content/abc/welcome.html
Actual scenario : abc.com/welcome.html is redirecting to /libs/cq/core/content/welcome.html and throwing 404 as it is denied
Expected scenario : abc.com/welcome.html should internally redirect to /content/abc/welcome.html
So, first precedence is always given for AEM welcome page.
Is there any solution for this ?
Please try out /etc/map mapping for this scenario. It allows for domain mapping so you can put entries which allow you to map exact domain. One more advantage is that /etc/map respects runmodes so you can pretty much create this for any environment.
Please refer https://sling.apache.org/documentation/the-sling-engine/mappings-for-resource-resolution.html and http://blog.magmalabs.io/2016/07/26/how-to-use-internal-redirects-in-aem.html
An entry like below would work;