[jira] [Resolved] (SLING-7785) Sling Dynamic Include: Allow Caching of Synthetic Resources

["Robert Munteanu (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-7785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Munteanu resolved SLING-7785.
------------------------------------
    Resolution: Fixed

Fixed with [sling-org-apache-sling-dynamic-include commit fb16171|https://github.com/apache/sling-org-apache-sling-dynamic-include/commit/fb16171]


> Sling Dynamic Include: Allow Caching of Synthetic Resources
> -----------------------------------------------------------
>
>                 Key: SLING-7785
>                 URL: https://issues.apache.org/jira/browse/SLING-7785
>             Project: Sling
>          Issue Type: Improvement
>    Affects Versions: Dynamic Include 3.1.0
>            Reporter: Andreas
>            Assignee: Robert Munteanu
>            Priority: Major
>             Fix For: Dynamic Include 3.1.2
>
>
> Due to the need to append the resource type as a suffix for virtual resources, AEMs Dispatcher is not able to cache those requests. The Dispatcher interprets the URL as having no extension, which makes it uncachable. Example:
> {code}
> <!--#include virtual="/content/test/www/gb/en/_jcr_content/root/header/menu.sdi.html/x/wcm/components/static/menu" -->{code}
> Since Sling also [allows dots in the suffix|https://sling.apache.org/documentation/the-sling-engine/url-decomposition.html#examples] adding a fake extension is possible to make it cacheable. Allowing to configure the extension makes it flexible enough to either use TTL or AEM Dispatchers Invalidation with different rules per extension.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)