[jira] [Commented] (SLING-8110) Take *extensions" service property into account for path-mounted servlets

["Bertrand Delacretaz (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-8110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16986974#comment-16986974 ] 

Bertrand Delacretaz commented on SLING-8110:
--------------------------------------------

I have suggested on our dev list using a new {{sling.servlet.resolution = strict}} service property to activate the "extensions" and "methods" properties when resolving path-mounted servlets, to keep backwards compatibility while enabling the stricter behavior. 

I don't think taking "selectors" into account is really useful but that's a detail, my key concern at this point is how to manage backwards compatibility.

Let's see what people think.

> 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)