Hi, Unfortunately I will have to cancel this release and start again. The fix for SLING-11722 [0] was too restrictive for Sling, when we think about how server-side rendering components are actually assembled. While in theory we are breaking the RequestDispatcher specification, our scripting model only functions based on runtime composition of the rendering model, where the main script doesn’t necessarily set all the headers or the status code.
I will still leave the two properties like they are, for applications that can work in this strict mode, but I will relax the implementation for the content type override [1] that it doesn’t automatically include the behaviour of protecting the header/status code override, but rather augments it. Thanks, Radu [0] - https://issues.apache.org/jira/browse/SLING-11722 [1] - https://github.com/apache/sling-org-apache-sling-engine/commit/5d8df33#diff-b732a751667da27420710cff218f7a66354e9530b2871a480425f9899f157caaR29 > On 9 Dec 2022, at 11:15, Radu Cotescu <r...@apache.org> wrote: > > Hi, > > We solved 1 issue in this release: > https://issues.apache.org/jira/browse/SLING/fixforversion/12352612 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2705/ > > You can use this UNIX script to download the release and verify the > signatures: > https://gitbox.apache.org/repos/asf?p=sling-tooling-release.git;a=blob;f=check_staged_release.sh;hb=HEAD > > Usage: > sh check_staged_release.sh 2705 /tmp/sling-staging > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] 0 Don't care > [ ] -1 Don't release, because ... > > This majority vote is open for at least 72 hours. > > Regards, > Radu Cotescu
