[
https://issues.apache.org/jira/browse/SLING-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger reassigned SLING-2619:
----------------------------------------
Assignee: Carsten Ziegeler
This refactoring introduced a property to register the filter with the new Http
Service Whiteboard support of Apache Felix. This allows registering Http
Service level filters as services provided the Http Service implements the
Apache Felix ExtHttpService.
Maybe Carsten can point to an issue related to this change (or create one after
the fact ;-) ).
> ReferrerFilter declares no scope
> --------------------------------
>
> Key: SLING-2619
> URL: https://issues.apache.org/jira/browse/SLING-2619
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Affects Versions: Security 1.0.0
> Reporter: Martin Wehner
> Assignee: Carsten Ziegeler
>
> The ReferrerFilter currently doesn't define a sling.filter.scope property in
> its service registration, so it isn't part of any Sling filter chain and
> thereby effectively deactivated by default. The scope property (request) was
> removed in a refactoring in Revision 1155355 ("Use global filter instead of
> Sling filter"), perhaps by mistake.
> If it was done on purpose, how is the filter supposed to be invoked now?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
