You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Joerg Hoh (Jira)" <ji...@apache.org> on 2021/09/14 07:07:00 UTC

[jira] [Updated] (SLING-10810) new status code should not be set if response is already comitted

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

Joerg Hoh updated SLING-10810:
------------------------------
    Summary: new status code should not be set if response is already comitted  (was: new response code should not be set if response is already comitted)

> new status code should not be set if response is already comitted
> -----------------------------------------------------------------
>
>                 Key: SLING-10810
>                 URL: https://issues.apache.org/jira/browse/SLING-10810
>             Project: Sling
>          Issue Type: Improvement
>          Components: Engine
>    Affects Versions: Engine 2.7.8
>            Reporter: Joerg Hoh
>            Assignee: Joerg Hoh
>            Priority: Major
>             Fix For: Engine 2.7.10
>
>
> If the response is already committed, a new response should not be set, but it should only be warned.
> Otherwise the status code logged in the Sling instance will taken from the ResponseImpl object, which is different from the statuscode which is sent to the client.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)