You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (Jira)" <ji...@apache.org> on 2021/07/12 18:39:00 UTC
[jira] [Resolved] (SLING-10597) Simplify setup of resource
resolution mappings
[ https://issues.apache.org/jira/browse/SLING-10597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Munteanu resolved SLING-10597.
-------------------------------------
Resolution: Fixed
Fixed in https://github.com/apache/sling-org-apache-sling-starter/pull/27
> Simplify setup of resource resolution mappings
> ----------------------------------------------
>
> Key: SLING-10597
> URL: https://issues.apache.org/jira/browse/SLING-10597
> Project: Sling
> Issue Type: Improvement
> Components: Starter
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Priority: Minor
> Fix For: Starter 12
>
>
> Creating the base path for resolution mapping entries ( {{/etc/map/http}} , see https://sling.apache.org/documentation/the-sling-engine/mappings-for-resource-resolution.html#root-level-mappings ) would make creating mapping entries simpler.
> This should be created in the Sling Starter OOTB. I would not create an {{https}} entry for now, since TLS-enabled Sling entries require manual set up, and probably Sling is used with an upstream server that handles TLS termination anyway.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)