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 (Jira)" <ji...@apache.org> on 2023/07/13 12:34:00 UTC

[jira] [Resolved] (SLING-11964) DefaultErrorHandler must not reset response

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

Carsten Ziegeler resolved SLING-11964.
--------------------------------------
    Resolution: Fixed

https://github.com/apache/sling-org-apache-sling-servlets-resolver/commit/0f9151e3d30e3b6ead6056ad51c5121d8a49f80b

> DefaultErrorHandler must not reset response
> -------------------------------------------
>
>                 Key: SLING-11964
>                 URL: https://issues.apache.org/jira/browse/SLING-11964
>             Project: Sling
>          Issue Type: Bug
>          Components: Servlets
>    Affects Versions: Servlets Resolver 2.9.12
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>            Priority: Major
>             Fix For: Servlets Resolver 2.9.14
>
>
> The Sling Engine is ensuring that the response is already reset before the ErrorHandler is invoked. As there might be error filters running between that reset and the ErrorHandler, the ErrorHandler must not reset the response again. Otherwise it would wipe out whatever the filters had already done to the response



--
This message was sent by Atlassian Jira
(v8.20.10#820010)