[SLING-10810] new status code should not be set if response is already committed

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Engine 2.7.8
• Fix Version/s: Engine 2.7.10
• Component/s: Engine
• Assignee: Joerg Hoh
• Reporter: Joerg Hoh
• Created: 14/Sep/21 07:05
• Updated: 27/Sep/21 08:05
• Resolved: 14/Sep/21 16:32

Description

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.

Issue Links

• is related to: SLING-7813 SlingHttpServletResponseImpl should log when setStatus is called after it is committed