Dispatcher and multi domain sites | Community
Skip to main content
J
jakej40603950
Level 5
January 19, 2018
Solved

Dispatcher and multi domain sites

  • January 19, 2018
  • 1 reply
  • 1512 views

I was referring to this guide which explains 2 different approaches to setting up dispatcher for multi domain sites hosted on the same AEM repo:

Using Dispatcher with Multiple Domains

The two approaches in short:

1. Use AEM sling url mappings for rewriting the shortened domain URLs to full repo paths and use 3 different dispatcher farms - two for each of the domains (in case there are two domains) and one farm for invalidating cache.

2. Use webserver rewrites to translate the URLs. This requires just one dispatcher farm.

The document recommends the sling mapping approach. But the 2nd one seems easier and cleaner to me since it requires far less dispatcher configuration.

Any insights as to why the guide linked above promotes the first approach?

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 jakej40603950

nvm, one thing I missed was that sling mappings also cause links in the rendered html markup to be shortened. In the 2nd approach of using web server rewrites, you'd have to do the extra work of writing a custom link transformer to do this job.

I'll mark this as the answer unless someone disagrees.

1 reply

J
jakej40603950AuthorAccepted solution
Level 5
January 21, 2018

nvm, one thing I missed was that sling mappings also cause links in the rendered html markup to be shortened. In the 2nd approach of using web server rewrites, you'd have to do the extra work of writing a custom link transformer to do this job.

I'll mark this as the answer unless someone disagrees.

Terms & ConditionsAccessibility statement

Loading footer...