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?
Community Discussion
No comments yet. Be the first to start the discussion!
Community Discussion