How can I do both of these on AEMaaCS?
Views
Replies
Total Likes
hi @jayv25585659,
For AEMasCS you can determine if a file is served from the CDN or the Dispatcher by examining the HTTP response headers.
The Adobe-provided CDN (Fastly) in AEMaaCS typically adds a debug header that indicates the cache status: look for the X-Cache response header.
Values meaning:
In short, if the X-Cache header value is anything other than HIT (typically MISS or EXPIRED), the request has hit your Dispatcher/AEM Publish stack.
is there a way to know if the page is already in the dispatcher or had to be fetched from the publisher?
In managed services, it's easy to check this (as I mentioned above) since clients can login to the dispatcher.
Thanks again.
Views
Replies
Total Likes
You can also check the Last-Modified response header. If Date and Last-Modified are same then page is served from publisher, if not then it is either from CDN or dispatcher cache.
Hi @jayv25585659 ,
In AEM as a Cloud Service (AEMaaCS), you can’t directly access the dispatcher or CDN servers like in Managed Services, but you can still check where your content is served from using response headers.
To check if it’s served from the CDN (Akamai):
Look at the response headers in your browser’s Network tab — you’ll usually see something like:
X-Akamai-Cache: HIT → served from CDN cache
X-Akamai-Cache: MISS → fetched from AEM origin
To check if it’s served from the Dispatcher (AEM layer):
You can enable or review dispatcher-level headers such as:
X-Cache: HIT from cloudfront or X-Cache: MISS from cloudfront
X-Dispatcher-Info (if configured in your dispatcher config via clientheaders.any or dispatcher.any)
Since you don’t have SSH access to dispatcher in AEMaaCS, you must rely on response headers and AEM logs (Developer Console) to confirm caching behavior.
Use browser response headers — Akamai headers tell you if it’s from CDN, and dispatcher headers (if enabled) tell you if it’s from AEM cache.
Thank you..
Views
Replies
Total Likes
Views
Likes
Replies