You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (Updated) (JIRA)" <ji...@apache.org> on 2011/12/21 08:50:31 UTC

[jira] [Updated] (SLING-1140) Rewriter Filter not called when error is handled

     [ https://issues.apache.org/jira/browse/SLING-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler updated SLING-1140:
------------------------------------

    Affects Version/s: Extensions Rewriter 1.0.0
        Fix Version/s: Extensions Rewriter 1.0.2
    
> 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
>    Affects Versions: Extensions Rewriter 1.0.0
>            Reporter: Honwai Wong
>            Assignee: Carsten Ziegeler
>            Priority: Minor
>             Fix For: Extensions Rewriter 1.0.2
>
>         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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira