When we add a new or update a vanity URLs to the page and save the config. The changes are not reflected immediately. But after few hours later, we do a check again, then the vanity URL can be used.
I also did a check right after creating a new vanity URL for my page, on Sling Resource Resolver (/system/console/jcrresolver), but nothing was updated as I can observe. But after few hours, the new vanity URL has been appeared on Sling Resource Resolver mapping, and I can use this Vanity URL.
From what I understand, vanity URL should be reflected immediately after I created or updated the vanity URL. But now it's taking too long.
Is there anything wrong for my system? Any help would be greatly appreciated.
When you removed your vanity url from page properties, did you check that page's jcr:content node that sling:vanityPath property is removed or does it still exist even after removing from page properties?
Do you see that rule on 'Resolver Map Entries' or 'Mapping Map Entries' on jcrresolver?
I did notice that, the old rules in jcrresolver is still there even I removed vanity URLs for my page. Tried restarting the AEM instance but these rules are still there. Does something stuck so these rules cannot be removed?
Do you mean to say that the console "Sling Resource Resolver (/system/console/jcrresolver)" doesn't show you updated rules immediately or it appears in console but it doesn't work when you try to access it in browser (either via publish directly or dispatcher)?