On Tue, 19 Nov 1996 arager @
mcgraw-hill .
com wrote:
> Here's one way to test this [your mileage may vary, and your test
> candidate may suffer for a bit]:
>
> -With Netscape [others would prob. work well also] pick a site outside
> your proxy that already seems somewhat slow/busy [www.aol.com comes to
> mind].
> -After loading the URL, hold down on <CTRL> <R> (reload) for about 30
> seconds. This will make gobs of requests and should make the server
> really busy.
> -Netscape should show the message "connect: server xx.xx.com
> contacted, waiting for reply" for at least 45secs.....wait a few
> minutes [depends on the server] and take a look at your logs. If you
> didn't crash the server with this load, then you should see an entry
> in your logs for a failed connection from your test host.
I appreciate that the intent of this procedure is honest, and meant for
genuine expansion of knowledge. But, I am getting a good chuckle over
seeing a procedure on the /firewalls/ list that could be interpreted as a
denial-of-service attack by the recipient web site... ;-)
- Stephen Shipman
-------------------
seshipma @
syrinx .
org
Follow-Ups:
References:
|
|
