Static css or js resources of a proxied clientlib causes an unwanted versioned clientlibs cache refresh

[wimsymons]

Required Information

• [x] AEM Version, including Service Packs, Cumulative Fix Packs, etc: 6.4.4.0
• [x] ACS AEM Commons Version: 3.19.0
• [x] Reproducible on Latest? yes

Expected Behavior

When there is a <script> tag or a <link> tag pointing to a static JS/CSS resource of a proxied clientlib (e.g. /etc.clientlibs/some/clientlib/resources/some-resource.js), the proxied clientlibs cache should not be reloaded.

Actual Behavior

When such a link is found, a lookup for a clientlib is done for (following the example above) some/clientlib/resources/some-resource, which doesn't exist and causing the proxied clientlibs cache to be reloaded for no reason. This causes extra stress on the instance.

Steps to Reproduce

• Create a proxied clientlib as described in https://helpx.adobe.com/be_nl/experience-manager/6-4/sites/developing/using/clientlibs.html
• In your page template add a snippet like this:

  <script type="text/javascript" src="/etc.clientlibs/some/clientlib/resources/some-resource.js"></script>

Links

• Static resource access through clientlib proxy: https://helpx.adobe.com/be_nl/experience-manager/6-4/sites/developing/using/clientlibs.html#LocatingaClientLibraryFolderandUsingtheProxyClientLibrariesServlet

[wimsymons]

Hi @davidjgonzalez, thanks for merging this into master, but there is no sign of the milestone this will be in. In what release will this be? 4.5.1 or 4.6.0? And again, any timings on the next release?