Venkat,
On 7/26/24 08:06, Venkateswararao Dama wrote:
Even Tomcat 9.0.91 version with JDK 17 and application running on
Windows 2022 server has same caching issues
Okay.
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
Is that a question or a statement? Are you saying that JAAS *is*
working, or *is not* working?
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.
Is this related to JAAS, or unrelated? It's best to handle one issue at
a time. So if the HTTP response headers are the biggest problem for you,
let's start there. If something else is more important, let's deal with
that, first.
So what's your biggest issue?
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.
What behavior are you expecting (specifically)? What behavior are you
seeing?
What other differences do you have between your working environment and
your non-working environment?
For example, if you are using TLS in your working production environment
but your non-working testing environment has no TLS, that's important
information to have.
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
