Well, so much for that theory. __Secure-JSESSIONID still sets the
sessionCookiePath to /. I even removed the entire session-config from the
web.xml and turned on copyXML to extract the secure#Foo.xml out to the
conf/Catalina/localhost folder. Based on the documentation, if I don't set
sessionCook
To give more context we originally moved to use __Host-JSESSIONID but were
seeing issues with the cookie getting overwritten when switching between
application contexts on the same host. I thought the routeid would play a
part in keeping the session cookies separate, but the browsers apparently
do
I think I just figured it out. __Host- doesn't allow for setting a path to
anything other than /.
It would have been nice if Tomcat would have logged an error instead of
silently failing, or forcing the path to / and not saying anything. That
would have saved me a ton of time.
--
Thanks,
Dan
O
Which one wins the catalina-base/conf/web.xml or the
Webapp/WEB-INF/web.xml.
I just noticed that the one under catalina base contains:
30
Or do they get merged?
Thanks,
Dan
On Thu, Jan 25, 2024 at 7:00 PM Dan McLaughlin wrote:
> Does anyone know what class we would crank the log level u
Does anyone know what class we would crank the log level up to see why
Tomcat would ignore cookie-config in our web.xml?
We are using Tomcat 10.1.18. Our app WAR is named secure#Foo.war. We've
always depended on the name of the WAR to name the Context Path/Name.
The only reason I'm messing with
On 25/01/2024 13:55, Tobias Blum (Fujitsu) wrote:
Hello together,
we have updated the Tomcat from Version 9.0.65 to Version 9.0.79.
We are running tomcat on Windows Server 2019
Our Tomcat Version is delivered with SAP BusinessObjects.
We have configured for our Web Application which runs on t
Hello together,
we have updated the Tomcat from Version 9.0.65 to Version 9.0.79.
We are running tomcat on Windows Server 2019
Our Tomcat Version is delivered with SAP BusinessObjects.
We have configured for our Web Application which runs on the Tomcat the SAML2
Authentication, after the updat