If i have a page with
https://localhost:4502/content/myproject/us/en/home/test-page.html
The above page contains a component which will add a selector
https://localhost:4502/content/myproject/us/en/home/test-page.model.html
model- selector
i have added a vanity url for the above page as /aempage
when i access the endsite url for the above page as https://localdev.example.com/vanityurl
https://localdev.example.com/aempage -> it redirects to 404 page
How do i implement vanity url in the above case
Solved! Go to Solution.
Views
Replies
Total Likes
@Shwetha1994 Does http://localhost:4502/aempage works for you?
Since the vanity URLs are working in the author/ publish instance, it's not an issue related to selectors. Basically, dispatcher level additional configuration has to be done for new vanity URLs to be picked up. This is explained here: https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/configuring/dispatcher-c... and you can also follow the 2nd link that Brian shared to configure vanity URLs in dispatcher
Take a look at these two articles:
And I don't think the out of the box vanity URL will work with selectors, it only works with the .HTML extension.
@Shwetha1994 Does http://localhost:4502/aempage works for you?
Since the vanity URLs are working in the author/ publish instance, it's not an issue related to selectors. Basically, dispatcher level additional configuration has to be done for new vanity URLs to be picked up. This is explained here: https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/configuring/dispatcher-c... and you can also follow the 2nd link that Brian shared to configure vanity URLs in dispatcher
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies