Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Dispatcher x Vanity URL

Level 2
Level 2

[sorry if this post is duplicated, but I cannot find the one I posted earlier today]

Hi all,

On my scenario I have a few hundred pages, and each page have a vanity URL assigned without extension (eg.: native AEM path is /content/site/language-code/product-type/country/state/city/product-instance.html and vanity path URL is /city/product-instance or even /marketing-appealing-url).

We have new pages being created and activated on a daily basis, and this information is relevant because I won't be able to change httpd.conf or dispatcher.any with the same frequency as pages are created.

Here are the two problems I am facing (I know I'll have more, but these two are the main ones...):

1) I learned by observation and also from another topic I read today in this forum ( that extension-less are not cached by the dispatcher.

On a site where ALL pages have extension-less vanity URLs, this is a problem, because no page will be cached.

Does anybody have an approach to cache those pages, even if it involves some development effort?

2) The documentation for dispatcher configuration status that we need to deny access to everything, and then allow for individual paths that the user needs access to enter the website (eg.: /content/*, /etc/clientlibs/*, etc). But also it states that one may need to grant access to vanities individually.

In my scenario I'll have to grant access to do the other way: grant access to everything, and then deny for the sensitive paths, as we won't be able to re-configure dispatcher each time a new vanity is added.

Is there a complete list of what must have access denied on Dispatcher?

Thanks a lot for your attention and time.

0 Replies