On 8/9/21 10:24 AM, Mark Thomas wrote:
Future versions of Tomcat won't see this issue but if the customer is prepared to update Tomcat to fix this issue then they might as well just update Java (assuming that is indeed sufficient to fix this).
Given that they currently seem to be happy as clams on their currently installed Tomcat 7, and that we've only been updating customers to Tomcat 8 in order to proactively deal with any security complaints that might come up, they can presumably wait for a Tomcat 8 that has the relevant fix.
And this customer is not in any particular hurry for updating *anything* (a trait I share).
Any idea when a Tomcat 8 with the relevant fix might come out? -- JHHL --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
