[
https://issues.apache.org/jira/browse/SLING-7759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16529587#comment-16529587
]
Nicolas Peltier commented on SLING-7759:
----------------------------------------
[~jsedding] agreed some consistency would be nice here. In the end servlets &
filters being tightly coupled with the {{RequestPathInfo}} instance's values.
However "registration properties" for a servlet or a filter should not be the
same exactly. For a servlet it should be generally much more exclusive than for
a filter.
* Adding multiple paths & prefix, while we have a path pattern might be enough
& simpler (even if inconsistent). may be sling.filter.pathPattern (that would
be the same as sling.filter.pattern i'd keep for )
* I think suffix still makes sense,
* resource type, why not :-)
* selector, extension, and method should MV, agreed
> add other "patterns" than path for filters
> ------------------------------------------
>
> Key: SLING-7759
> URL: https://issues.apache.org/jira/browse/SLING-7759
> Project: Sling
> Issue Type: Improvement
> Components: Engine
> Affects Versions: Engine 2.6.12
> Reporter: Nicolas Peltier
> Assignee: Nicolas Peltier
> Priority: Major
>
> adding additional patterns to filters (right now {{sling.filter.pattern}}
> allows to include them based on path only):
> - path passes if sling.filter.pattern (i propose we keep it for legacy & add
> sling.filter.pattern.path for consistency with what follow) regexp matches
> current path,
> - selector passes if sling.filter.pattern.selector is in the selector chain,
> - method passes if sling.filter.pattern.method is equals to curren method,
> - suffix passes if sling.filter.pattern.suffix regep matches current suffix
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
