Submit Feedback
Legacy Knowledge Base
Published Sep. 10, 2025

JS file caching

Written By

Apsara Raheja

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • How to enable the cache for the JS file?
  • On each page refresh, all default JS is getting called, impacting site performance.

Environment

  • Liferay Paas
  • Liferay Quarterly Release

Resolution

  • While refreshing the page, all default JS is getting called due to the Private - no cache header since it forces the caching agents to check resource freshness before serving. Inspect the browser, navigate to the network tab, and check the index.js file header, Private - no-cache header will be displayed.

  • There are currently no OOTB methods to change the cache configuration for JS files as it is hard-coded. Check this for more information: LPD-18034

  • Also, changing the cache configuration will impact the operations that require updating JS resources on the server, such as: Deploying new versions of third-party developments, Product upgrades, and Product patching.

  •  Additionally, if translations in the portal have been modified, which are used in cached JS files, then end-users might not see the latest translations in the UI.

Additional Information

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?