Debugging cache status of a page | Community
Skip to main content
New Participant
December 31, 2023
Solved

Debugging cache status of a page

  • December 31, 2023
  • 2 replies
  • 673 views

Imagine a scenario where a web page on site is not reflecting the latest changes, and you suspect caching issues. How would you go about debugging and determining whether the issue is related to caching by the CDN, AEM Dispatcher, or the Publish instance? What specific tools or techniques would you use, and what key indicators would you look for in each case?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by aanchal-sikka

@aniketsi 

 

Please refer to https://techrevel.blog/2023/09/05/exploring-aem-request-and-response-headers-analysis-of-browser-cdn-and-dispatcher/ 

 

It explains about Cache-Control, X-Dispatcher-Info and X-Cache-Info headers which has help you debug caching of a page.

The debugging steps are explained at Exploring AEM Request and Response Headers: Analysis of Browser, CDN and Dispatcher – Adobe Experience Manager Blog (wordpress.com)

2 replies

aanchal-sikka
aanchal-sikkaAccepted solution
New Participant
December 31, 2023

@aniketsi 

 

Please refer to https://techrevel.blog/2023/09/05/exploring-aem-request-and-response-headers-analysis-of-browser-cdn-and-dispatcher/ 

 

It explains about Cache-Control, X-Dispatcher-Info and X-Cache-Info headers which has help you debug caching of a page.

The debugging steps are explained at Exploring AEM Request and Response Headers: Analysis of Browser, CDN and Dispatcher – Adobe Experience Manager Blog (wordpress.com)

Aanchal Sikka
New Participant
December 31, 2023

Hi @aniketsi 

 

First, test the page in Author (View as published), whether the feature is working fine or not.

Then, use IP based URL of one of the publish environment. (Even you can hit all the IP's of publisher env.)

Then, verify by using prod dispatcher URL. This will hit one of the multiple publish environment. If the feature works fine here, then try to hit the page using Dispatcher IP url. Example: 10.12.13.14:8080/en/hello.html  Just to make sure that issue is in CDN or from dispatcher.