You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (JIRA)" <ji...@apache.org> on 2018/11/15 12:42:00 UTC

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

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

Konrad Windszus commented on SLING-8110:
----------------------------------------

This limitation is clearly mentioned in http://sling.apache.org/documentation/the-sling-engine/servlets.html#servlet-registration and also affects "selectors" and "methods". All those are not taken into account for path based registration of servlets!

> 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
>            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
(v7.6.3#76005)