[
https://issues.apache.org/jira/browse/SLING-8110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17000047#comment-17000047
]
Bertrand Delacretaz commented on SLING-8110:
--------------------------------------------
The discussion is at [1] and my takeaways are:
* Add a module config flag for a default value of the {{strict}} resolver option
* Increase the {{org.apache.sling.servlets.resolver / Version="1.1"}}
capability of this module to {{1.2}} to signal the new, backwards-compatible
behavior.
* Update the Sling OSGi Annotations so to include this new parameter _and_
require that {{1.2 Version}} capability if it is used. This will prevent OSGi
bundles which require this capability from starting
I also created SLING-8936 to improve the test coverage before implementing
this, as the code I need to change is not covered this module's tests.
[1]
https://lists.apache.org/thread.html/202c695070feaacd47c972adee04ae07346dfe33b40a8f00bb0831d7%40%3Cdev.sling.apache.org%3E
> 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)
