I found the solution myself. @AmitVishwakarma was almost right — but the simplest approach turned out to be asking the CDN provider to rewrite the headers. That way, I didn't have to redo thousands of redirects.Thanks for the support!

Than you for the explanation @AmitVishwakarma  I suppose I have no other option but to implement the redirects using the Host as you suggested. I had tried setting the Host header in the Akamai request to the origin (publish-xxx-xxx, which is behind Fastly), but Fastly responded with a 421 error. Ju...

Than you for the reply, i think that would work, however, i am trying to understand if this behavior is expected, or if there is something wrongly configured in the CDN or Apache. Updating the redirects as you suggested may work but i have thousands of redirects, so i am hesitant to update all of th...

Hi there, I'm currently using AEM as a Cloud Service and have Akamai configured on top of it. Akamai is correctly routing traffic to my AEM publish instance at: "publish-pxxx-exxxx.adobeaemcloud.com" and everything seems to work fine at first glance. However, I'm encountering an issue with redirects...

Hi @TarunKumar thank you for the response, but as i said this is AEMaaCS, where you dont have access to the dispatcher server, so i cannot verify the .stat files. Also, the debugging header is not valid in AEMaaCS just on premise, so if you have any other suggestion it would be highly welcome

Hi there, The issue:Every time I publish a page, I don’t see the content updated at the publish-xxx-xxx URL (dispatcher). Things I’ve tried to troubleshoot:Disabled the CDN cache (Fastly) to ensure it's not cached there (didn’t work).Disabled the "enableTTL" config in the dispatcher (didn’t work).Se...