The proposed Apache Tomcat 10.1.53 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.52 are:

- Relax HTTP/2 header validation and respond to invalid requests with
  a stream reset or a 400 response as appropriate rather then with a
  connection reset.

- Fix bug 69964: Respect the configured cipher order, which was no
  longer respected following the addition of TLS 1.3 specific cipher
  configuration. TLS 1.3 ciphers will always be first in the list.

- Update Tomcat Native to 2.0.14 and increase the recommended version to
  2.0.14

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.53/

The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1585

The tag is:
https://github.com/apache/tomcat/tree/10.1.53
https://github.com/apache/tomcat/commit/f3d5786aa1bd6c2a78d666afc89b2a4570f66593

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]

Reply via email to