Hi Tomcat Users Group, Even Tomcat 9.0.91 version with JDK 17 and application running on Windows 2022 server has same caching issues, in 9.0.91 version of Tomcat Callback handlers are working as it expected in JAAS authentication according to Tomcat 9.0.91 change log, is this true, in Tomcat 9.0.91 why response headers are in Private mode instead of expiring Jan 1st 1970, shall I adjust response headers to private mode, max-expires to 6000. How to handle response headers in my Spring MVC application from expire mode to private, even though I am using expires zero, whey it is ignoring, what tag I need to use to get back to backward compatibility in my Spring MVC application not caching from browsers, JAAS authetification validates User Name/Password properly from Tomcat container. Please help me here when you get a chance, your help here mostly appreciated.
Best Regards Venkat ________________________________ From: venkatd...@hotmail.com Shanthisowjanyadama9 <venkatd...@hotmail.com> Sent: Friday, July 26, 2024 1:45 AM To: users@tomcat.apache.org <users@tomcat.apache.org> Subject: Tomcat 9.0.80 Server Issues. Hi Tomcat Uses group, My Java Spring MVC application works great with Tomcat 9.0.50, when I moved Tomcat version from 9.0.50 to 9.0.80 my spring MVC java web application was broken, JAAS authentication is not working as it expected, all of a sudden chrome browser(s) caching web application and response headers not expiring like before, I am looking for a workaround for this issue here. I am also wondering why backward compatibility is not maintained in Tomcat Server end when I switch from one version of Tomcat to another version. Your help here is greatly appreciated. Best Regards Venkat