You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (Jira)" <ji...@apache.org> on 2020/01/15 09:18:00 UTC

[jira] [Updated] (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:all-tabpanel ]

Bertrand Delacretaz updated SLING-8110:
---------------------------------------
    Summary: Take "extensions" service property into account for path-mounted servlets  (was: Take *extensions" service property into account for path-mounted 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
>            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)