[ https://issues.apache.org/jira/browse/SLING-11911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus resolved SLING-11911. ------------------------------------- Resolution: Fixed Fixed in https://github.com/apache/sling-org-apache-sling-servlets-resolver/commit/b3eb8e642b71fea0c9cbd74b5f71b707e5d8e7ab. > Use proper resource resolving in Sling Servlet Resolver web console > ------------------------------------------------------------------- > > Key: SLING-11911 > URL: https://issues.apache.org/jira/browse/SLING-11911 > Project: Sling > Issue Type: Improvement > Components: Servlets > Affects Versions: Servlets Resolver 2.9.12 > Reporter: Konrad Windszus > Assignee: Konrad Windszus > Priority: Major > Fix For: Servlets Resolver 2.9.14 > > > For historical reason the servlet resolver web console didn't actually > resolve the resource to correctly decompose the URL but always used a > heuristics. With SlingUriBuilder providing the method > {{SlingUriBuilder.rebaseResourcePath()}} this now became much simpler and we > can easily do the resolving in the web console in the same way like it is > done in Sling. -- This message was sent by Atlassian Jira (v8.20.10#820010)