Legacy Knowledge Base
Published Sep. 10, 2025

Content Delivery Network (CDN) configuration "cdn.dynamic.resources.enabled=false" is not working

Written By

Michael Warren Young

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

  • After setting cdn.dynamic.resources.enabled=false, Liferay is still accessing some CSS and JavaScript from the CDN URLs configured in cdn.host.http= and cdn.host.https=

Environment

  • Liferay Portal
  • Liferay DXP

Resolution

  • If the properties cdn.host.http= and/or cdn.host.https= are set, then they will be used for static content (for HTTP and HTTPS respectively). The property cdn.dynamic.resources.enabled= does not disable these properties for static content, it only controls whether they will be user for dynamic content in addition to static content.
  • If you disable the first two properties as well, either by entering blank values for them or commenting them out in your portal-ext.properties, then Liferay will no longer load JavaScript or CSS from the CDN.
  • Note that in Liferay DXP 7.0+, these settings can also be configured in Control Panel > Configuration > Instance Settings > Configuration. If they are updated in the control panel, this setting will override any settings in your portal-ext.properties.
Did this article resolve your issue ?

Legacy Knowledge Base