[
https://issues.apache.org/jira/browse/SLING-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13035365#comment-13035365
]
Antonio Sanso commented on SLING-1140:
--------------------------------------
attaching a patch [0] SLING-1140. I have used sling.filter.scope and
service.ranking rather than filter.scope and filter.order since it seems they
are deprecated now.
[0]
https://issues.apache.org/jira/secure/attachment/12479581/SLING-1140-asanso-patch.txt
> Rewriter Filter not called when error is handled
> ------------------------------------------------
>
> Key: SLING-1140
> URL: https://issues.apache.org/jira/browse/SLING-1140
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Reporter: Honwai Wong
> Priority: Minor
> Attachments: SLING-1140-asanso-patch.txt
>
>
> In case an errorhandler is triggered (e.g. 404 occurred), the Rewriter Filter
> and thus custom filters in the pipeline are ignored. Filters should be
> triggered even when an error occurred beforehand.
> Use-case:
> - have a custom 404-errorhandler in place,
> /apps/sling/servlet/errorhandler/404.jsp
> - do a RequestDispatcher#forward to a resource whose output is usually being
> rewritten
> --> filters are ignored, output of forwarded resource is not rewritten
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
