You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "John Mitchell (JIRA)" <ji...@apache.org> on 2018/10/01 12:15:00 UTC
[jira] [Created] (SLING-7964) Make the suffix optional for included
resources
John Mitchell created SLING-7964:
------------------------------------
Summary: Make the suffix optional for included resources
Key: SLING-7964
URL: https://issues.apache.org/jira/browse/SLING-7964
Project: Sling
Issue Type: Improvement
Affects Versions: Dynamic Include 3.1.2
Reporter: John Mitchell
I'm using Sling Dynamic Includes to cache re-usable content for search results. That is to say that the search results are dynamic - but the content of the individual results are not.
The structure of the page was that the original request from the browser had a suffix to indicate the search query:
{code:java}
/path/to/search/results/page.html/query/for/the/search{code}
The search results were inserted using non-synthetic page resources and a included selector to render a specific form of that page. The problem was that the original suffix of the parent request was included in the SSI include - so that there were numerous versions of the child resource, and therefore didn't achieve the cache hit ratio we were looking for.
This PR adds a new option that makes this optional (current behaviour maintained by default) - so that this "reverse" dynamic include use case is catered for.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)