[
https://issues.apache.org/jira/browse/SLING-8110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17031736#comment-17031736
]
Bertrand Delacretaz commented on SLING-8110:
--------------------------------------------
At [commit
cab578f13|https://github.com/apache/sling-org-apache-sling-servlets-resolver/commit/cab578f13c9c7c2e9479baf7d4bac691e10ace70]
the core of this is implemented.
To finalize this feature I need to also implement the SLING-9055
{{SlingServletPathsStrict}} along with the corresponding OSGi capabilities
changes so that code that uses that annotation requires the appropriate version
of the {{o.a.s.servlets.resolver}} bundle.
> Take "extensions" service property into account for path-mounted servlets
> -------------------------------------------------------------------------
>
> Key: SLING-8110
> URL: https://issues.apache.org/jira/browse/SLING-8110
> Project: Sling
> Issue Type: Improvement
> Components: Servlets
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
> Priority: Minor
>
> If a Sling Servlet has both _paths_ and _extensions_ service properties,
> currently the _paths_ take over and the _extensions_ are ignored.
> This has caused confusion with users who have set both properties on a
> servlet - my initial thought was to reject such illegal combinations, but a
> colleague rightly notes that it would make sense to honor the _extensions_
> property as well, and only route requests to that servlet if there's a match
> on the extension.
> This requires more analysis, for now I'm just creating this ticket to remind
> us to have another look.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
