You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Honwai Wong (JIRA)" <ji...@apache.org> on 2009/10/08 10:25:31 UTC
[jira] Created: (SLING-1140) Rewriter Filter not called when error
is handled
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. 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.
[jira] Commented: (SLING-1140) Rewriter Filter not called when
error is handled
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903064#action_12903064 ]
Felix Meschberger commented on SLING-1140:
------------------------------------------
This is probably related to SLING-1213, where filters may be scoped. In this case the rewriter filter may be scoped such to also be called in case of error processing.
> 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.
[jira] Updated: (SLING-1140) Rewriter Filter not called when error
is handled
Posted by "Honwai Wong (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (SLING-1140) Rewriter Filter not called when error
is handled
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger updated SLING-1140:
-------------------------------------
Component/s: (was: Engine)
Affects Version/s: (was: Engine 2.0.4)
Component/s: Extensions
This is probably more an issue of the Rewriter module
> 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
>
> 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.