[
https://issues.apache.org/jira/browse/SLING-9222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17062609#comment-17062609
]
Bertrand Delacretaz commented on SLING-9222:
--------------------------------------------
bq. Shouldn't the same be supported for resource type based servlets?
The mechanism is a bit different in that case as it's a best match algorithm:
if there's no specific servlet for a .html extension for example, the next more
generic servlet is used for resource-based servlet resolution. So that might
not be backwards compatible?
For the path-mounted servlets we're fine due to the new
{{sling.servlets.paths.strict}} property required to enable these stricter
selection features, so backwards compatibility is not a problem.
> Support requiring empty extensions or selectors in paths.strict mode
> --------------------------------------------------------------------
>
> Key: SLING-9222
> URL: https://issues.apache.org/jira/browse/SLING-9222
> Project: Sling
> Issue Type: Improvement
> Components: Servlets
> Affects Versions: Servlets Resolver 2.6.4
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
> Priority: Minor
> Fix For: Servlets Resolver 2.6.6
>
>
> The SLING-8110 {{sling.servlets.paths.strict}} mode should support requiring
> an empty set of selectors or and empty extension for a path-based servlet to
> be selected.
> I'll implement this using a special {{.EMPTY.}} value for the
> {{sling.servlet.selectors}} and {{sling.servlet.extensions}} properties,
> which indicates that the servlet is only selected if the corresponding value
> is empty.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
