Thanks, Mark. Submitted <
https://bz.apache.org/bugzilla/show_bug.cgi?id=68934>
On Tue, Apr 16, 2024 at 4:44 AM Mark Thomas wrote:
> It would be worth creating an enhancement request for this in Bugzilla
> to ensure the request doesn't get forgotten about.
>
> Mark
>
>
> On 16/04/2024 01:06,
It would be worth creating an enhancement request for this in Bugzilla
to ensure the request doesn't get forgotten about.
Mark
On 16/04/2024 01:06, Baron Fujimoto wrote:
From our perspective, it needn't be super timely. It would be more for
forensic confirmation that there's something we
>From our perspective, it needn't be super timely. It would be more for
forensic confirmation that there's something we should consider. I think a
hysteresis behavior would be compatible with this.
On Mon, Apr 15, 2024 at 12:00 AM Mark Thomas wrote:
> On 11/04/2024 21:28, Baron Fujimoto wrote>
On 11/04/2024 21:28, Baron Fujimoto wrote> I was thinking it would be
something that would be left on in a live> system. We can set these
parameters, so it would be useful to know if we
were hitting the set limits.
For the connection limit:
How timely do you need the information to be? It is
I was thinking it would be something that would be left on in a live
system. We can set these parameters, so it would be useful to know if we
were hitting the set limits.
I'm not sure I fully grasp how this additional logging presents a
significant incremental DOS risk. I mean, if an attacker is
Baron,
On 4/9/24 16:33, Baron Fujimoto wrote:
I'm investigating occasional 503 errors for our CAS service running in a
Tomcat 10.1.x container. The 503s appear to correlate with some traffic
spikes at the same time.
The connector is configured as follows:
Can Tomcat log info such as
