What is the problem you are trying to solve?
When using the new CMS Basic Documents in Liferay DXP, the system setting:
System Settings → Documents and Media → File Entry Friendly URL → Enable Friendly URL With Extension
does not work as expected.
For a document uploaded as:
Plain Text
cool.png
Zobrazit více řádků
the following friendly URL works:
Plain Text
/documents/d/asset-library-35783/cool
Zobrazit více řádků
but the extension-based URL:
Plain Text
/documents/d/asset-library-35783/cool.png
Zobrazit více řádků
returns a 404 error, even though Enable Friendly URL With Extension is enabled.
This creates an inconsistency between the legacy Documents and Media implementation and the new CMS Basic Documents implementation. It also reduces the value of the configuration setting, since enabling it has no effect for CMS Basic Documents.
As a result, organizations face challenges with migrations, predictable URL design, integrations, CDN rules, caching mechanisms, and consistency across content management solutions within Liferay.
What is your project about? (e. g. Intranet, Partner Portal, Enterprise Website, etc)
We are using Liferay as a public enterprise website and content management platform.
The website delivers content and downloadable assets to external users, with a strong preference for user-friendly and predictable URLs. We are also evaluating and adopting the newer CMS capabilities introduced in recent DXP releases and would like to use CMS Basic Documents as a modern replacement for legacy Documents and Media functionality.
Consistent document URLs are important for integrations, CDN configuration, content delivery, SEO-related URL management, and migration scenarios from legacy content repositories.
What is your proposed solution? (optional)
When Enable Friendly URL With Extension is enabled, CMS Basic Documents should support friendly URLs that include the original file extension.
For example, both URLs should successfully resolve to the same document:
Plain Text
/documents/d/asset-library-35783/cool
Zobrazit více řádků
and
Plain Text
/documents/d/asset-library-35783/cool.png
Zobrazit více řádků
Ideally, the extension-based URL should become the preferred canonical format when the setting is enabled.
This would:
- Align CMS Basic Documents with the behavior expected from the configuration setting.
- Improve consistency between legacy Documents & Media and the new CMS.
- Simplify migrations to CMS Basic Documents.
- Provide more predictable and user-friendly URLs.
- Improve compatibility with CDN, caching, proxy, and integration scenarios that rely on file extensions.
- Reduce confusion for administrators and developers who expect the setting to behave consistently across document management features.