vanity url's are not working immediately | Community
Skip to main content
M
Mahesh_Gunaje
Level 7
January 25, 2024
Solved

vanity url's are not working immediately

  • January 25, 2024
  • 1 reply
  • 931 views

Hello All,

 

I have referred this site to configure Vanity URL:

 

https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/configuring/dispatcher-configuration.html?lang=en

Added these details in the dispatcher

/vanity_urls {
/url "/libs/granite/dispatcher/content/vanityUrls.html"
/file "/tmp/vanity_urls"
/delay 300
}

 

created vanity_urls file under /tmp folder with write permission.

Uploaded and installed the “vanityurls-component” package on our AEM publish environment.

 

Then, Once I add vanity URL to a page and published this page.  Also, added Vanity URL for 10 pages and published those pages. Then, I have restarted Apache server. Now, all the page works fine with Vanity URL.  Now, if I add vanity URL for a page and then published the page. Now, Vanity URL is not working for this newly published page. Waited for 10-20 min. Still, no luck.  I am not sure, why Apache server restart is required to work for Vanity URL?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Raja_Reddy

Hi @mahesh_gunaje 

1.Dispatcher Cache:
The Apache dispatcher often caches responses to improve performance. When you add or modify Vanity URLs, the dispatcher cache might need to be refreshed to reflect these changes. Restarting the Apache server is one way to clear the cache.

2.Dispatcher Configuration:
Ensure that your dispatcher configuration is set up correctly. Verify that the /vanity_urls section in your dispatcher configuration is accurately pointing to the vanity URL configuration file, and that the dispatcher is configured to read this file.

Cache Invalidation:
Instead of restarting the entire Apache server, consider using cache invalidation mechanisms provided by the dispatcher. You may have the option to selectively invalidate the cache for specific URLs or paths, avoiding the need for a full server restart.

3.Dispatcher Flush Agent:
AEM provides a mechanism for flushing dispatcher caches using the Flush agent. You can configure the Dispatcher Flush agent in AEM to clear the cache for specific pages or paths when changes are made. Ensure that the Flush agent is set up and working properly.

1 reply

Raja_Reddy
Community Advisor
Raja_ReddyCommunity AdvisorAccepted solution
Community Advisor
January 26, 2024

Hi @mahesh_gunaje 

1.Dispatcher Cache:
The Apache dispatcher often caches responses to improve performance. When you add or modify Vanity URLs, the dispatcher cache might need to be refreshed to reflect these changes. Restarting the Apache server is one way to clear the cache.

2.Dispatcher Configuration:
Ensure that your dispatcher configuration is set up correctly. Verify that the /vanity_urls section in your dispatcher configuration is accurately pointing to the vanity URL configuration file, and that the dispatcher is configured to read this file.

Cache Invalidation:
Instead of restarting the entire Apache server, consider using cache invalidation mechanisms provided by the dispatcher. You may have the option to selectively invalidate the cache for specific URLs or paths, avoiding the need for a full server restart.

3.Dispatcher Flush Agent:
AEM provides a mechanism for flushing dispatcher caches using the Flush agent. You can configure the Dispatcher Flush agent in AEM to clear the cache for specific pages or paths when changes are made. Ensure that the Flush agent is set up and working properly.

    Terms & ConditionsAccessibility statement

    Loading footer...