Expand my Community achievements bar.

Guidelines for the Responsible Use of Generative AI in the Experience Cloud Community.

what are the possible reasons for dispatcher caching when we are using Akamai

Avatar

Community Advisor

Hi All

 

What are the possible reasons Akamai redirects every request to the dispatcher for secured and non-secured content, and how does the dispatcher serve that content?

 

 

Thanks

KNan

3 Replies

Avatar

Community Advisor

Hi @KNan ,

Pls check  the TTL settings in Akamai . Depending on the TTL value Akamai should be able to server the requests until it is expired.  Below are few best practices from Akamai perspective :-

  • Have default TTL rules at Akamai.
  • If necessary, enable Honor Cache-control and Expires so that AEM can dictate the TTL to Akamai. The headers could be set to a lower time bound so that cache purge or invalidate requests are never required. 

Check the below links. It may be helpful .

AEM & Akamai Integration - AEM Corner

Adobe CQ / AEM & Akamai integration best practices

 

Thanks,

Somen

Avatar

Employee Advisor

Hi,

with "secured" and "unsecured" content, are you using permission sensitive caching?

Avatar

Administrator

@KNan Did you find the suggestions helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!



Kautuk Sahni