[
https://issues.apache.org/jira/browse/SLING-7310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16289513#comment-16289513
]
Henry Kuijpers commented on SLING-7310:
---------------------------------------
For our use-case, using JSI is for now a viable workaround.
But imho there should not be a difference between the initial request and the
requests after that (after caching), in terms of the HTML content that is
returned.
> Sling Dynamic Include: When HTML file is initially created, the includes are
> not processed
> ------------------------------------------------------------------------------------------
>
> Key: SLING-7310
> URL: https://issues.apache.org/jira/browse/SLING-7310
> Project: Sling
> Issue Type: Bug
> Affects Versions: Dynamic Include 3.0.0, Dynamic Include 3.0.2
> Reporter: Henry Kuijpers
>
> When creating the initial HTML for a page that has SSI tags, for some reason
> the includes are not processed.
> I.e. the page is served with
> {code}<!--#include
> virtual="/path/to/content/_jcr_content/root/main/some-component.caching-prevented.html"
> -->{code}
> However, when I then refresh that page (load the HTML file from the docroot),
> the include *is* processed and the sub-request ends up in the backend system.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
