0 for me. I would probably prefer that the SLING-12124 changes not be reverted as leaving the old behavior could be somewhat of a security risk. For example, I could put enough extra dots in the url to push some details of the address off the right edge of the browser's address bar in order to obscure information from the user in order to trick them into doing something they wouldn't otherwise do if the canonical address was fully visible.
Perhaps there is a convenient way that the SLING-12124 behavior could be made optional via some configuration flag? Or at least some feedback somewhere to nudge the end user into using a well formed address? Regards, -Eric On Fri, Dec 15, 2023 at 3:56 AM Carsten Ziegeler <[email protected]> wrote: > Hi, > > We solved 1 issue in this release > https://issues.apache.org/jira/browse/SLING-12201 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2823/ > > 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 2823 /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 > Carsten > -- > Carsten Ziegeler > Adobe > [email protected] >
