QuestionQ10

Adobe Experience Manager Sites Architect Master

A website built on AEM as a Cloud Service (AEMaaCS) uses browser caching of JavaScript and CSS files to improve page-load times. After caching is enabled, QA testers observe that newly deployed components lack newly developed features and styling, even several hours after deployment. Further analysis identifies stale CSS and JavaScript files in the browser cache as the root cause.

What steps would an AEM architect take first to resolve this issue?

Explanation

Strict clientlib versioning appends a serialized content hash to client-library URLs. When CSS or JavaScript changes, AEM generates a new URL, so a refreshed HTML page references the updated asset instead of a stale browser-cached copy. In AEM as a Cloud Service, this setting is controlled through the Adobe Granite HTML Library Manager OSGi configuration and is enabled by default.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!