AEM Dispatcher considers sitemap as vanity URL

Avatar

Avatar

tatvam

Avatar

tatvam

tatvam

10-09-2020

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?

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar

Shashi_Mulugu

MVP

Avatar

Shashi_Mulugu

MVP

Shashi_Mulugu
MVP

10-09-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-co...

 

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.

 

tatvam
@sashi_mulugu does dispatcher treat xml extensions as vanity URLs? All other URLs are not treated like this and are getting rendered fine.
Shashi_Mulugu
@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.
Shashi_Mulugu
So it could be coincidence that when you request sitemap.xml , at same dispatcher might have called this service or you might have filter for either sitemap or xxl extensions in dispatcher which is forcing dispatcher to check for vanity service everytime
tatvam

Found the answer, but it took a while dealing with environments with restrictive permissions.
1) The dispatcher filter rules were correct. 
2) No need to remove the vanity URLs section
3) Found that the DNS routed the traffic to a different vhost in this multi-vhost environment
4) And this routed the traffic subsequently to wrong dispatcher farm.

 

In short, dispatcher behaved correctly as expected - meaning it got a 404 in filters and thus routed to vanity URLs - just that it happened in the wrong dispatcher farm.

Answers (0)