Dan,
On 2/1/24 11:54, Dan McLaughlin wrote:
I was able to identify the problem - there was a session configuration with
cookie configuration in the catalina-base/web.xml file.
catalina-base/conf/web.xml?
I did mention on 26 Jan that this wasn't a good idea and could be
causing this kind of p
Hey Mark,
I was able to identify the problem - there was a session configuration with
cookie configuration in the catalina-base/web.xml file.
I just wanted to suggest that it would be great if logging could be enabled
to show not only what the parameters were set to, but also where the
values cam
On 27/01/2024 14:38, Dan McLaughlin wrote:
Hey Mark,
If you see a bug report, then that will mean I was able to reproduce it. I
see different behaviors in our local docker environment. Still, it's
nowhere as complex as our production environment--where everything is
clustered and behind load
Hey Mark,
If you see a bug report, then that will mean I was able to reproduce it. I
see different behaviors in our local docker environment. Still, it's
nowhere as complex as our production environment--where everything is
clustered and behind load balancers, etc... It probably would be easier
On 26/01/2024 22:22, Dan McLaughlin wrote:
Hey Konstantin,
Thanks for the reply.
I synced the source last night. I haven't had a chance to step through with
a debugger yet. But the only way I could get the Cookie Path set was to
modify the context.xml and add sessionCookiePath to every applicat
Hey Konstantin,
Thanks for the reply.
I synced the source last night. I haven't had a chance to step through with
a debugger yet. But the only way I could get the Cookie Path set was to
modify the context.xml and add sessionCookiePath to every application. I'm
pretty sure this wasn't how things w
Dan,
On 1/26/24 02:44, Dan McLaughlin wrote:
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
пт, 26 янв. 2024 г. в 04:01, Dan McLaughlin :
>
> 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
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
13 matches
Mail list logo
