[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jetty-dev] Invalid Ping Frame Rate with Jetty 9.4.21 v20190926
|
I would seriously doubt that there were 1200 clients connected.
Is it possible that some older browser sends too many pings?
Is there an easy way to find out how many clients are connected?
We count the number of sessions but that is a different thing in a way.
thanks,
Michele
Hi,
On Fri, Oct 18, 2019 at 7:53 PM Michele Rossi <michele.rossi@xxxxxxxxx> wrote:
>
> hi,
> I am not sure how many clients we had connected but probably more than 20.
Still, having each one sending a PING every second or so looks like a
DDoS attack.
> Each client keeps a cometd long poll connection open that probably meant loads of http2 connections.
Well, not "loads", just 1 per client.
> Yes reverting to the previous build fixed it.
> If this becomes configurable how do I know what number to set it to in advance?
You should first understand who's sending all those PINGs as it really
looks like an attack.
I would imagine a client needing to send a PING every, say, 1 minute.
To exceed the default limit in this case you'd need 1200 clients.
Do you have such numbers?
--
Simone Bordet
----
http://cometd.org
http://webtide.com
Developer advice, training, services and support
from the Jetty & CometD experts.
_______________________________________________
jetty-dev mailing list
jetty-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jetty-dev
--
Sent from Gmail Mobile
