Hi @daniel-strmecki I tried a curl command similar to this, where the request is not sent to direct publish url, instead publish url with a content path.There we are getting a 200 as expected, not 302.curl https://publish-pXXXXXX-eXXXXXX.adobeaemcloud.com/content/project/home.html -I --header "X-For...

Hi @daniel-strmecki During troubleshooting, allowed X-Forwarded-Host header in clientheaders,  DispatcherUseForwardedHost - Set to On.Curl command is returning 302 still, and the X-Forwarded-Host response header in aem-debug, is showing the publish url, not the domain.Is testing through the curl com...

Hi @SantoshSai How can we validate this curl command is behaving as expected? Are we looking for 200 status?And in dispatcher, I have used this ' DispatcherUseForwardedHost ${FORWARDED_HOST_SETTING} '  in dispatcher_vhost.confAnd declared this FORWARDED_HOST_SETTING variable in global.vars as On.For...

Hi @daniel-strmecki Yes, I have a farm file and vhost for the project. And all the rewrites and rules are correctly working with the hostname mentioned in the virtualhost except Akamai.Regards,Ranjith

Hi,My requirement is to use Akamai as CDN for my AEMaaCS project.Followed this documentation from Adobe CDN in AEM as a Cloud Service | Adobe Experience Manager.Akamai we configured as per the sample vendor configurations.I created a edge key and deployed it through cdn.yaml file (attached screensho...