Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Won't Fix
-
Security 1.0.0
-
None
-
None
Description
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?
Attachments
Issue Links
- relates to
-
SLING-2664 Register ReferrerFilter as global filter using http whiteboard
- Resolved