> the heavy user. If no one else is using the server, what's the problem?
Just one example: I don't like paying for someone on a cable modem to
try out his new download toy by starting a download of our site before
he goes to bed, only to wakeup and find out it ran all night and still
didn't fini
On Mon, 14 Oct 2002, Jim Wilcoxson wrote:
> > I have a lame hack I do which is to check the ns_server information to see if
>there is already a process running from the peer address via a filter. It works for
>me since mine is an internal app and we have no proxy.
>
> The problem with this app
> I have a lame hack I do which is to check the ns_server information to see if there
>is already a process running from the peer address via a filter. It works for me
>since mine is an internal app and we have no proxy.
The problem with this approach IMO is that there are no options at
that p
I don't know how to do it, but it would be *really* cool if IP
addresses could be rate-limited and serialized inside the AOLServer
core without having to resort to proxying every incoming connection
through another piece of software.
Several things would be needed:
1. An interface to set/query t
I have a lame hack I do which is to check the ns_server information to see if there is
already a process running from the peer address via a filter. It works for me since
mine is an internal app and we have no proxy.
In the real world, there are proxies, so my hack would never work.
>>> [EMAI
Hello,
What is the best way to limit the number of simultaneous requests from
one ip-address? Is it possible to achieve that via aolserver
configuration? Or do I have to look into something like snort?
Last Friday I got about 10reqs/sec from one funny user who wanted to
copy the entire site. She
