Cache invalidation on Adobe Faslty cdn using purge API with X-Forwarded-Host will also Invalidate cache on customer managed Akamai CDN? | Community
Skip to main content
K
kgpraveen
December 9, 2024
Solved

Cache invalidation on Adobe Faslty cdn using purge API with X-Forwarded-Host will also Invalidate cache on customer managed Akamai CDN?

  • December 9, 2024
  • 4 replies
  • 878 views

using purge API call to invalidate the adobe managed CDN cache with " X-Forwarded-Host" will invalidate or refresh the Cache on customer managed CDN automatically.
we are using TTL based approach for cache invalidation on both adobe cdn & custom CDN. We want to invalidate the cache immediately before TTL expires on a publishing the content.

curl
-X PURGE "https://publish-p1234-e5467.adobeaemcloud.com/resource-path" \
-H 'X-AEM-Purge-Key: "my_purge_key"
-H 'X-AEM-Edge-Key: "my_edge_key" 
-H 'X-Forwarded-Host: "my_forwarded_domain"

 

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 EstebanBustamante

Hi,

 

I think you might be misreading the documentation. You can purge the Adobe CDN cache (Fastly) from the Customer CDN (Akamai), but not the other way around. The docs shared and comments from others refer to the first scenario, where you flush the Fastly cache from the Akamai (Customer CDN) by adding the necessary headers.

 

 

Hope this clears up your doubts.

4 replies

arunpatidar
Community Advisor
arunpatidarCommunity Advisor
Community Advisor
December 9, 2024

Hi @kgpraveen 

Yes, it seems so according to the CDN cache documents

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/content-delivery/cdn-cache-purge 

Arun Patidar
    daniel-strmecki
    Community Advisor and Adobe Champion
    daniel-strmeckiCommunity Advisor and Adobe Champion
    Community Advisor and Adobe Champion
    December 9, 2024

    Hi @kgpraveen,

    every CDN has a different cache purging API. I wasn't unaware there was a feature to purge customer CDN as well.

    Please let us know if it works as expected and which CDN you are using.

     

    Good luck,

    Daniel

      TarunKumar
      Community Advisor
      TarunKumarCommunity Advisor
      Community Advisor
      December 9, 2024

      Hi @kgpraveen 

       

      Yes, you can try to invalidate Adobe CDN from customer CDN by using below headers:-

      •   Use X-Forwaded-for    
      • Use the "X-AEM-Edge-Key" header:
      When sending a purge request to the Adobe CDN from your customer CDN, include the "X-AEM-Edge-Key" header with the correct authentication value. 
       
      • Provide necessary details:
        Depending on the setup, you might also need to include other headers like "X-Forwarded-Host" to identify the origin of the request
         
         
        -Tarun
        EstebanBustamante
        Community Advisor and Adobe Champion
        EstebanBustamanteCommunity Advisor and Adobe ChampionAccepted solution
        Community Advisor and Adobe Champion
        December 10, 2024

        Hi,

         

        I think you might be misreading the documentation. You can purge the Adobe CDN cache (Fastly) from the Customer CDN (Akamai), but not the other way around. The docs shared and comments from others refer to the first scenario, where you flush the Fastly cache from the Akamai (Customer CDN) by adding the necessary headers.

         

         

        Hope this clears up your doubts.

        Esteban Bustamante
          Terms & ConditionsAccessibility statement

          Loading footer...