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
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
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
On Fri, Jan 26, 2024 at 1:57 PM Christopher Schultz
wrote:
>
> Aryeh,
>
> On 1/20/24 4:19 AM, Aryeh Friedman wrote:
> > Top posting since my comments are not 100% relevant to the issue in
> > the thread (i.e. related but not in detail).
> >
> > It would be nice if Tomcat published EOL's since
To whom it may concern,
On 1/21/24 2:59 PM, support wrote:
I receive the Windows error below every time I try to start the Tomcat
Windows service after modifying the server.xml file to require TLS. I
used the instructions below and other online sources to find the proper
syntax to modify
Aryeh,
On 1/20/24 4:19 AM, Aryeh Friedman wrote:
Top posting since my comments are not 100% relevant to the issue in
the thread (i.e. related but not in detail).
It would be nice if Tomcat published EOL's since there are
applications (like HIPAA webapps [I do remote cardiac monitoring])
that
See AbstractAccessLogValve (which AccessLogValve overrides)
Then you could override AbstractAccessLogValve.createAccessLogElement()
which has
case 'q':
return new QueryElement();
To possible do doing something like
case 'q':
return new
I want to obfuscate values of query params for certain URLs, however, I
would still like to log the request. Therefore, I cannot use the existing
conditionif/conditionunless attributes that AccessLogValve provides.
Sincerely,
Manak Bisht
On Fri, Jan 26, 2024 at 6:18 PM Mark Thomas wrote:
> On
On 26/01/2024 10:46, Manak Bisht wrote:
Hi,
I am trying to extend the AccessLogValve to modify logging behaviour for
certain URLs. However, I don't have access to the request object in the
AccessLogValve API. So, I am left with regex matching on the CharArrayWriter
message object. Is there a
My bad - AccessLogValve also supports that feature too
- *%{xxx}r* write value of ServletRequest attribute with name xxx (escaped
if required, value ?? if request is null)
https://tomcat.apache.org/tomcat-9.0-doc/config/valve.html#Access_Logging
-Tim
On Fri, Jan 26, 2024 at 7:23 AM Tim
It depends on what you are trying to accomplish. ExtendedAccessLogValve is
a
little more flexible where you can write out arbitrary request
attributes but still format the request like the standard access
log. So you could have a filter set the value and not need to
write your own access logger.
Hi,
I am trying to extend the AccessLogValve to modify logging behaviour for
certain URLs. However, I don't have access to the request object in the
AccessLogValve API. So, I am left with regex matching on the CharArrayWriter
message object. Is there a better way to do this?
Sincerely,
Manak
Hi Mark,
I tried running your *cluster-test* war example on a stock 8.5.98
installation, however, I am facing the same issue. Session sync does not
trigger on restarting a node. Could you please share your configuration?
Sincerely,
Manak Bisht
пт, 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
14 matches
Mail list logo