Re: Shutting Down Tomcat (9.0.97) Service Throws System Error 1067

2024-11-19 Thread Chuck Caldarale
> On Nov 19, 2024, at 08:16, Kostyantyn Krakovych > wrote: > > Hi Team, > > Could you please suggest or advice regarding the following? > > 1. We use Tomcat 9.0.87 as a windows service. It works fine with our > application. > 2. To fix security vulnerabilities we are upgrading Tomcat to ver

Re: 10.1.25 -> 10.1.33 - no more content-* headers in HEAD responses

2024-11-19 Thread Pawel Veselov
On Wed, Nov 20, 2024 at 1:26 AM Pawel Veselov wrote: > > Hello. > > Upgrading Tomcat from 10.1.25 to 10.1.33 caused our sanity tests to > fail as the "content-length" header field is no longer present in the > HEAD responses. > > The application explicitly sets the content-length header on HEAD re

10.1.25 -> 10.1.33 - no more content-* headers in HEAD responses

2024-11-19 Thread Pawel Veselov
Hello. Upgrading Tomcat from 10.1.25 to 10.1.33 caused our sanity tests to fail as the "content-length" header field is no longer present in the HEAD responses. The application explicitly sets the content-length header on HEAD requests. The change is traced to this commit: commit 8e786a8eda Aut

Shutting Down Tomcat (9.0.97) Service Throws System Error 1067

2024-11-19 Thread Kostyantyn Krakovych
Hi Team, Could you please suggest or advice regarding the following? 1. We use Tomcat 9.0.87 as a windows service. It works fine with our application. 2. To fix security vulnerabilities we are upgrading Tomcat to version 9.0.97. 3. The upgraded service works fine except when shutting down/stopp