The proposed Apache Tomcat 10.1.50 release is now available for
voting.
All committers and PMC members are kindly requested to provide a vote if
possible. ANY TOMCAT USER MAY VOTE, though only PMC members votes are
binding. We welcome non-committer votes or comments on release builds.
The notable changes compared to 10.1.49 are:
- Add strictSNI attribute on the Connector to allow matching the
SSLHostConfig configuration associated with the SNI host name to the
SSLHostConfig configuration matched from the HTTP protocol host name.
Non matching configurations will cause the request to be rejected. The
attribute default value is true, enabling the matching.
- Correct a regression introduced in 9.0.109 that broke some clustering
configurations.
- Fix manager status output for applications which failed to start,
and add deployment state for all applications.
- Fix returning connections to jdbc-pool when the underlying connection
has already been closed.
For full details, see the change log:
https://nightlies.apache.org/tomcat/tomcat-10.1.x/docs/changelog.html
Applications that run on Tomcat 9 and earlier will not run on Tomcat 10
without changes. Java EE applications designed for Tomcat 9 and earlier
may be placed in the $CATALINA_BASE/webapps-javaee directory and Tomcat
will automatically convert them to Jakarta EE and copy them to the
webapps directory.
It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-10/v10.1.49/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1574
The tag is:
https://github.com/apache/tomcat/tree/10.1.50
https://github.com/apache/tomcat/commit/cd6d685800b0e46797325866dee2c9a78fc8e69c
Please reply with a +1 for release or +0/-0/-1 with an explanation.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
