@berliant @  @Albin_Issac You are absolutely correct! This does not look ideal, however there are multiple factors that lead us to this setup. There are few more options on the table that we are considering, however, I wanted to explore this option before we simply drop it. I have been able to conne...

@kautuk_sahni thanks for facilitating.

ok @Jörg_Hoh thanks for the update. I will mark this complete.

Hello Guys, Need your suggestions on a Apache/Dispatcher setup. (Please see the attached diagram)  ScenarioThe customer has the standard AEM Publish and Apache web servers (shown as #1 in the diagram) already setup and there are multiple websites hosted here.For one new site, there is a need to acce...

@Jörg_Hoh This did not work for me. I checked it twice.I am using Apache 2.4.29 on Ubuntu 18.x for server #2 and Apache 2.4.28 on RHEL 7.5 for server #1.DispatcherUseServerNameInVia 0I could still see the similar exceptions as before complaining about declining the call as the request is already ser...

I will try this.

Let me give this a try @Jorg and @Shashi_Mulugu .

shashi1223Outermost Apache (#2) has the Rewrite rules with the [PT] flag to pass on the request to outermost dispatcher (#2) and then further pass the request to innermost Apache (#1) and from there to (dispatcher #1) -> Publish.The rewrite rules look like this,RewriteRule ^/$ /content/aem-repositor...

@Shashi_Mulugu No, the dispatcher #2 are apache+dispatcher. No CDN in this equation.

@Shashi_Mulugu Yes, i tried that and problem I faced is dispatcher (#1) declines the request as request is already processed by the dispatcher #2. This is by Dispatcher design.