AEM Dispatcher considers sitemap as vanity URL | Community
Skip to main content
tatvam
tatvam
Level 2
September 10, 2020
Solved

AEM Dispatcher considers sitemap as vanity URL

  • September 10, 2020
  • 1 reply
  • 2643 views

We have sitemap configured as 

/en/sitemap.xml

This is working as expected in the publisher. However while accessing from dispatcher, see the following the dispatcher log

Unable to fetch vanity URLs from [ip-address]:4503/libs/granite/dispatcher/content/vanityUrls.html: remote server returned: HTTP/1.1 404 Not Found [Thu Sep 10 21:37:51 2020] [I] [pid 79557] "GET /[path-to-en]/en/sitemap.xml" ! - 9ms [publishfarm/-]



It seems like the sitemap is treated as vanity URL. Any thoughts on how to prevent this?

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 Shashi_Mulugu

@tatvam thank you for helping the community grow. Are you using Vanity URLs in your project?

 

If yes you have to enable access to Vanity URL via dispatcher by following below helps Adobe doc:

https://docs.adobe.com/content/help/en/experience-manager-dispatcher/using/configuring/dispatcher-configuration.html#enabling-access-to-vanity-urls-vanity-urls

 

If you project/client not using or planning to use AEM Vanity URL then simply remove that section from publish farm.

 

When you enable this Vanity urls in dispatcher (yes in most cases) dispatcher will periodically checks the Vanity service hosted in aem publishers to get latest vanities and will apply to incoming requests. It is an expected behavior.

 

1 reply

Shashi_Mulugu
Community Advisor
Shashi_MuluguCommunity AdvisorAccepted solution
Community Advisor
September 11, 2020

@tatvam thank you for helping the community grow. Are you using Vanity URLs in your project?

 

If yes you have to enable access to Vanity URL via dispatcher by following below helps Adobe doc:

https://docs.adobe.com/content/help/en/experience-manager-dispatcher/using/configuring/dispatcher-configuration.html#enabling-access-to-vanity-urls-vanity-urls

 

If you project/client not using or planning to use AEM Vanity URL then simply remove that section from publish farm.

 

When you enable this Vanity urls in dispatcher (yes in most cases) dispatcher will periodically checks the Vanity service hosted in aem publishers to get latest vanities and will apply to incoming requests. It is an expected behavior.

 

    Shashi_Mulugu
    Community Advisor
    Shashi_MuluguCommunity Advisor
    Community Advisor
    September 11, 2020
    @tatvam, if you refer to documentation, it says, When access to vanity URLs is enabled, Dispatcher periodically calls a service that runs on the render instance to obtain a list of vanity URLs. Dispatcher stores this list in a local file. When a request for a page is denied due to a filter in the /filter section, Dispatcher consults the list of vanity URLs. If the denied URL is on the list, Dispatcher allows access to the vanity URL.
    Terms & ConditionsAccessibility statement

    Loading footer...