[
https://issues.apache.org/jira/browse/SLING-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Honwai Wong updated SLING-1140:
-------------------------------
Description:
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
was:
In case an errorhandler is triggered (e.g. 404 occurred), the Rewriter Filter
and thus custom filters in the pipeline. 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
> 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: Engine
> Affects Versions: Engine 2.0.4
> Reporter: Honwai Wong
> Priority: Minor
>
> 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.
-
You can reply to this email to add a comment to the issue online.
