Perrin Harkins wrote:
> > It's configurable so after
> > exceeding a threshold the client gets content from the shared memory
> > cache, and if a second threshold is exceeded (ok this guy is getting
> > REALLY irritating) then they get the 'come back later' message. They will
> > only get cached
If you're looking for limiting simultaneous requests to a URI resource
(and not the entire server, which can be handled by MaxClients), you may
be looking for mod_throttle_access. It can be found at
http://modules.apache.org/search?id=232.
Regards,
Christian
-
Christian Gilmore
T
> It's configurable so after
> exceeding a threshold the client gets content from the shared memory
> cache, and if a second threshold is exceeded (ok this guy is getting
> REALLY irritating) then they get the 'come back later' message. They will
> only get cached content if they exceed x number o
Geoffrey Young wrote:
> > Ken Miller wrote:
> >
> > There was a module floating around a while back that did request
> > limiting (a DOS preventional tool). I've searched the archives
> > (unsuccessfully), and I was wondering if anyone knows what the heck
> > I'm talking about.
>
> maybe you had
> Ken Miller wrote:
>
> There was a module floating around a while back that did request
> limiting (a DOS preventional tool). I've searched the archives
> (unsuccessfully), and I was wondering if anyone knows what the heck
> I'm talking about.
maybe you had Stonehenge::Throttle in mind?
http:
