/libs/granite/dispatcher/content/vanityUrls.html does not exist on AEM 6.4.3

7 replies
7136 views
Translate

Hi all,

According to the documentation at Configuring Dispatcher we no longer need to install the VanityURLS-Components package anymore on AEM instances > 6.3.

I just setup an AEM 6.4.3 instance and there is no /libs/granite/dispatcher/content/vanityUrls.html to be found.

Is the documentation just plain wrong?

Has it been moved to another path? Or must we still install the VanityURLS-Components package on AEM 6.4 instances?

Kind regards,

Wim

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

S

Sameer-BhaleraoAccepted solution

Employee

The only resolution which worked for me is to allow anonymous access to /libs/granite/dispatcher/content/vanityUrls.html

Once given, publisher is able to hit the url and cache the vanity_urls at its end. All other setup is as mentioned already like installing VanityURLS-Components to publisher.

W

wimsymonsvrtAuthor

Level 4

Indeed sameerb50449612 you are correct.

I didn't follow up on this thread, but you need to do 2 things:

install the VanityURLS-Components package on the publisher
apply your own ACL to allow read access to /libs/granite/dispatcher/content/vanityUrls for anonymous

Regards

Wim

Translate

S

Sameer-BhaleraoAccepted solution

Employee

The only resolution which worked for me is to allow anonymous access to /libs/granite/dispatcher/content/vanityUrls.html

Once given, publisher is able to hit the url and cache the vanity_urls at its end. All other setup is as mentioned already like installing VanityURLS-Components to publisher.

Translate

W

wimsymonsvrtAuthor

Level 4

So how is this suppose to work?

Translate

joerghoh

Employee

The behavior is perfectly ok, because /libs is locked down (and it is since quite a while).

Translate

W

wimsymonsvrtAuthor

Level 4

After installing the vanityurls-components package 1.0.2 the content appeared in CRX/DE, but the URL was not accessible for "everyone".

When I added an ACL to allow read on /libs/granite/dispatcher/content/vanityUrls, the unauthenticated http call to http://localhost:4502/libs/granite/dispatcher/content/vanityUrls.html works as expected.

Strange the package doesn't contain such an ACL rule.

On the other hand, I read the Replication agent configuration documentation again. There, they speak of an "Alias update" option you should enable to send vanity path invalidation requests to Dispatcher. The same should be done on your Dispatcher Flush Agent running on the publish instance as documented here. I will give that a try that as well, without using the vanityurls-components package.

Translate