what are the possible reasons for dispatcher caching when we are using Akamai | Community
Skip to main content
New Participant
September 20, 2024
Question

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

  • September 20, 2024
  • 3 replies
  • 851 views

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

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

3 replies

kautuk_sahni
Employee
October 9, 2024

@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
joerghoh
Employee
September 21, 2024

Hi,

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

somen-sarkar
New Participant
September 20, 2024

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