How do you test Akamai configuration with AEMaaCS before DNS is live?

[Luca_Moreau]

I'm setting up Akamai for AEMaaCS using the sample vendor config with edge keys. Is there a way to test Akamai → Dispatcher → AEM routing without pointing the live DNS yet?

[SantoshSai · Accepted solution]

Hi @Luca_Moreau,

Can you try testing it by making curl requests directly to the AEM publish URL and passing the headers manually:

curl https://publish-<program>-<env>.adobeaemcloud.com \
-H "X-Forwarded-Host: yourdomain.com" \
-H "X-AEM-Edge-Key: <your-key>" \
-H "x-aem-debug: edge=true" -v

Also, ensure that your dispatcher’s virtual hosts are configured with yourdomain.com. You’ll only see a full round-trip via Akamai once DNS points to Akamai, but this curl method helps test the setup in isolation.

Hope that helps!

Regards,
Santosh

[Luca_Moreau]

Thanks, that worked! Just curious - once DNS is pointed to Akamai, is there a way to confirm that requests are actually hitting Akamai and not going directly to publish?

[SantoshSai]

Yes, a good way to confirm is by checking response headers.

When the request is served via Akamai, you’ll usually see headers like:

• X-Akamai-Request-ID

• X-Cache (you might see TCP_HIT or TCP_MISS)

• Via (sometimes includes Akamai info)

Also, Chrome DevTools > Network tab to inspect those headers for live DNS-based calls.

[RanjithR1]

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.conf

And declared this FORWARDED_HOST_SETTING variable in global.vars as On.
For setting the X-Forwarded-Host, is this the only configuration we need to do, or is there anything other than this?