According to Randal L. Schwartz:
> > "Leslie" == Leslie Mikesell <[EMAIL PROTECTED]> writes:
>
> Leslie> How about an option to redirect to a different machine instead? I've
> Leslie> considered digging out an old, slow 386 to handle greedy clients
> Leslie> without obviously denying service
> "Leslie" == Leslie Mikesell <[EMAIL PROTECTED]> writes:
Leslie> How about an option to redirect to a different machine instead? I've
Leslie> considered digging out an old, slow 386 to handle greedy clients
Leslie> without obviously denying service to them.
Most evil spiders I've see don't
According to Randal L. Schwartz:
>
> So, I modified my throttler to look at the recent CPU usage over a
> window for a given IP. If the percentage exceeds a threshold, BOOM
> they get a 503 error and a correct "Retry-After:" to tell them how
> long they're banned.
How about an option to redirec
On 16 Nov 1999, Randal L. Schwartz wrote:
> So, here's source. Peer review requested - I'm probably turning
> this in for my next WebTechniques column...
It would be nice if the various package vars were configurable from a
.conf file. Certainly there's no reason to hard code the history dir a
On Tue, 16 Nov 1999, Jeffrey W. Baker wrote:
> Also how does this IP-based tracking work in practice? People who are
> behind corporate firewalls present dual problems: one person can map to
> several IP addresses if the firewall uses a cluster of proxies, and one
> IP can map to many people. A
> "Jeffrey" == Jeffrey W Baker <[EMAIL PROTECTED]> writes:
Jeffrey> That's a nifty module. I suggest that you alter your
Jeffrey> threshold slightly. Instead of setting a fixed percentage of
Jeffrey> CPU time, you should also consider the overall load. I know
Jeffrey> I wouldn't care if on
"Randal L. Schwartz" wrote:
>
> OK, I went one better. I now have CPU-percentage-based throttling.
> The big problem on my site was not bandwidth, but how quickly the
> loadav would go up when I got hammered by things like "Teleport Pro".
> Hey, if you haven't seen that, go see it. Be afraid.
OK, I went one better. I now have CPU-percentage-based throttling.
The big problem on my site was not bandwidth, but how quickly the
loadav would go up when I got hammered by things like "Teleport Pro".
Hey, if you haven't seen that, go see it. Be afraid. Be Very Afraid.
See http://www.tenmax.
On Tue, 16 Nov 1999, Matt Sergeant wrote:
> For the unique IP in _most_ firewall cases, take the last comma separated
> value of the X-Forwarded-For header: $r->headers_in->get('x-forwarded-for');
except for all the clients at 192.168.1.100 (etc).
So you would have to get into "real ip / forwar
At 23:26 16/11/1999 -0600, Leslie Mikesell wrote:
>According to Randal L. Schwartz:
>>
>> So, I modified my throttler to look at the recent CPU usage over a
>> window for a given IP. If the percentage exceeds a threshold, BOOM
>> they get a 503 error and a correct "Retry-After:" to tell them how
10 matches
Mail list logo
