This behaviour has been added via https://issues.apache.org/jira/browse/SLING-2724 <https://issues.apache.org/jira/browse/SLING-2724>, but I think that what happens with flush* is too drastic.
> On 15 Jun 2022, at 10:53, Radu Cotescu <[email protected]> wrote: > > Sure there is. However, in our case the dispatcher’s [1] and writer’s flush > [3] methods are the ones that fail, since they throw an exception if the > stream was closed. I don’t think this is correct. Flush should send the > content to the client and commit the response, but IMO should not throw if > the response has already been committed.
