Le 11/25/13 3:37 PM, Andrew Pennebaker a écrit :
> This is a good edge case to consider, as some script kiddy tools for
> attacking websites behave this way.
*Always*, I really mean *ALWAYS*, check your server's code against slow
clients. That's a sanity check you have to do to be sure that your
a
This is a good edge case to consider, as some script kiddy tools for
attacking websites behave this way.
On Fri, Nov 22, 2013 at 4:00 PM, Binole, Bill <
william.j.bin...@questdiagnostics.com> wrote:
> I was wondering how to handle a slow client. So say my client writes 100
> bytes and then 5 se
You should never assume that all of your data is available. If you work
with this, you can handle any speed client. I test everything against
simulated invalid packets and random latency.
On Nov 25, 2013 9:38 AM, "Andrew Pennebaker" wrote:
> This is a good edge case to consider, as some script ki
Hello, all!
I noted that, after receiving a given amount of data, the server
session is not able to close the connection properly.
A good connection with a small amount of data transferred looks like
the following:
==> Call to onExit callback.
[pool-3-thread-1] DEBUG org.apache.sshd.server.chann
