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
lmore
Team Lead
Web Infrastructure & Tools
IBM Software Group
-Original Message-
From: Ken Miller [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 14, 2002 12:14 PM
To: [EMAIL PROTECTED]
Subject: Request Limiter
There was a module floating around a while back that did request limiti
> 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
nge::Throttle in mind?
http://www.stonehenge.com/merlyn/LinuxMag/col17.html
>
> I thought it was on Matt Sergeant's web site, but for the life of me
> I can't remember what the url is.
>
> Can someone help?
>
> My next question would be, if I can't find the
e life
of me I can't remember what the url is.
Can someone help?
My next question would be, if I can't find the module, is what
phase would I place a request limiter? Should it just go at the head of
the PerlHandler chain, or earlier in the request phase?
(I do have 'the
