akamai page invalidation | Community
Skip to main content
New Participant
June 17, 2016
Solved

akamai page invalidation

  • June 17, 2016
  • 1 reply
  • 988 views

We use AEM 5.6 and have hooked into the replication agent an akami REST request to invalidate the url (and friendly url). This works great. What does not get invalidated is any clientlibs js or css that may be refrenced by the page (and modified). We then have to manually figure out the corresponding URL of the JS or CSS and invalidate (with another tool) .

 

Is there a way to figure out all the corresponding JS and css linked URL's to a page that should be included in the akamai invalidation request.

 

Hope this makes sense.

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 joerghoh

Hi,

Please use the "versioned clientlib feature" of ACS AEM Commons [1]. As you use AEM 5.6, you should use a version 1.x (as the current versions require at least AEM 6.0), see [2] for the latest version. Because then you don't need to invalidate any kind of CSS or JS, as with any change you get a different filename. 

Jörg

 

[1] https://adobe-consulting-services.github.io/acs-aem-commons/features/versioned-clientlibs.html

[2] https://github.com/Adobe-Consulting-Services/acs-aem-commons/releases/tag/acs-aem-commons-1.10.6

1 reply

joerghoh
joerghohAccepted solution
Employee
June 18, 2016

Hi,

Please use the "versioned clientlib feature" of ACS AEM Commons [1]. As you use AEM 5.6, you should use a version 1.x (as the current versions require at least AEM 6.0), see [2] for the latest version. Because then you don't need to invalidate any kind of CSS or JS, as with any change you get a different filename. 

Jörg

 

[1] https://adobe-consulting-services.github.io/acs-aem-commons/features/versioned-clientlibs.html

[2] https://github.com/Adobe-Consulting-Services/acs-aem-commons/releases/tag/acs-aem-commons-1.10.6