/libs/granite/dispatcher/content/vanityUrls.html does not exist on AEM 6.4.3 | Community
Skip to main content
W
wimsymonsvrt
Level 4
January 23, 2019
Solved

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

  • January 23, 2019
  • 7 replies
  • 7129 views

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.
Best answer by Sameer-Bhalerao

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.

7 replies

smacdonald2008
smacdonald2008
Level 10
January 23, 2019

We are looking into this. If the docs are wrong - we will log a bug,

    L
    Adobe Employee
    leoberliantAdobe Employee
    Adobe Employee
    January 23, 2019

    A similar question was answered at Re: Enabling Access to Vanity URLs ( vanityUrls.html )

      W
      wimsymonsvrtAuthor
      Level 4
      January 24, 2019

      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.

        joerghoh
        Adobe Employee
        joerghohAdobe Employee
        Adobe Employee
        January 24, 2019

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

          W
          wimsymonsvrtAuthor
          Level 4
          January 24, 2019

          So how is this suppose to work?

            S
            Adobe Employee
            Sameer-BhaleraoAdobe EmployeeAccepted solution
            Adobe Employee
            September 18, 2019

            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
              September 18, 2019

              Indeed sameerb50449612​ you are correct.

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

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

              Regards

              Wim

                Terms & ConditionsAccessibility statement

                Loading footer...