More info at https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/london-aem-user-group-recap-cloud-or-classic-navigating-aem-s/td-p/769950
Hi @Shashi_Mulugu Here we have similar thread but for 6.6 https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/why-upgrade-to-aem-6-6/m-p/759702
Hi @ReneDa
If you are using core components then it is added from /libs/core/wcm/components/page/v3/page/head.html
https://github.com/adobe/aem-core-wcm-components/blob/a0866659765c7225bb3139ed180cc7e90686c203/content/src/content/jcr_root/apps/core/wcm/components/page/v3/page/head.html#L21you have...
Hi @KONDISR
You can do redirect, redirect first event-name--12345 to event-name name and then forward request to intended origin.
Pipeline free redirect - https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/content-delivery/pipeline-free-url-redirects
...
Hi @KONDISR
Do you need to redirect when editing the page or for end user.
For Editing the page, you can create another EDIT button which will open page with universal Editor.
For end user, you need to write rules at CDN to forward traffic to different origins(AEM, EDS etc)
Hi @jayv25585659
Please check https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/deploying/configuring-osgi#osgi-configuration-property-formats
Hi @ArvindPa2
If everything looks good on all the publish instances then end user will see the same. The reason for not seeing the correct content is due to caching at various level like dispatcher or CDN or browser.
Hi @ryuushihou1990
Please check if this helps
https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/sites/authoring/sites-console/page-properties#on-off-time
https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/operations/replication#on-a...