Hi Jay,   AEM provides us with SlingRequestDispatcher[1], This would allow you to fire request from within your component code.   Following reply from the past seems to help too[2]   1 [https://github.com/apache/sling-org-apache-sling-engine/blob/master/src/main/java/org/apache/sling/engine/impl/req...

Hey Veena,   Does enabling day cq core debug filter and acs aem commons filter give you any hints as to how you can optimize your page better? Regards, Peter

Hi Abhishek,   In AEM as a Cloud Service you probably want to utilise Preview Service[1] this way you will show Authored content to any interested party before it goes to Live.   Preview has standard Publisher to render content and Dispatcher to cache content.   [1] https://experienceleague.adobe.co...

@kautuk_sahni kindly move this post to AEM Sites area.

Why do it on Publisher, would it not be better to do it in Webserver layer?   Regards, Peter 

Kindly attach screenshot with the error message. Peter

Hi TB3dock,   Both in regards to your first observation and your subsequent query,   It's all spelled here in fine print: Adobe Experience Manager as a Cloud Service | Product Description   Using Splunk forwarder to ingest logs and then doing maths via Splunk Dashboards to see the approx thresholds ...

Hi Manikanta,   Would suggest,   sling:match="(.*)cf#(.*)" sling:redirect="http://localhost:4502/editor.html$2"   Regards, Peter

Hi Tam,   Do you see any exceptions in your author logs? Regards, Peter

Hi Manikanta,   First of all we can configure AEM to open in Touch UI by default [1]   In addition we can configure Sling Redirect to redirect any request into cf to editor.html Thus any content author who may have bookmarked old page will be redirected to TouchUI alternative.   [1] user interface -...