[jira] Resolved: (SLING-1850) Make sure error response is sent back even if the response cannot be reset

["Felix Meschberger (JIRA)" <ji...@apache.org>]

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

Felix Meschberger resolved SLING-1850.
--------------------------------------

    Resolution: Fixed

Reverted the early-error-handling-abort change introduce in SLING-1842 in Rev. 1026351.

> Make sure error response is sent back even if the response cannot be reset
> --------------------------------------------------------------------------
>
>                 Key: SLING-1850
>                 URL: https://issues.apache.org/jira/browse/SLING-1850
>             Project: Sling
>          Issue Type: Bug
>          Components: Engine
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: Engine 2.1.2
>
>
> Along the lines of fixing SLING-1842 I also modified error handling to not send back any response data at all if the response has already been committed. Previously the error information was just written into the existing response regardless of whether the response has been committed or not.
> The problem is in the SlingRequestProcessorImpl.handleError methods which do nothing if the response has already been committed. This is probably fundamentally wrong and must be fixed.
> It is the task of the actual error handler to (a) check whether the response has already been committed and can be reset and (b) to decide whether to send back response data if the response is committed or not...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.