>>Yes, 0 would disable it. Looking at the logic that would indeed cause
it not to throttle anything.
As it was explained above, 0 would only eliminate hits based on
minhittime, not all hits. Too many hits would still add up and
throttle. Except they aren't for me. Or was the logic posted in this
thread incorrect?
This was posted above:
----------------------------------------
It looks like this:
if (age <= hitTimePeriod AND currentClientHitCount >= hitThreshold) {
throttled
} else if (lastHitDiffInMs > 10 AND lastHitDiffInMs < MinhitTime) {
quick throttled because the it's too fast of an access
quick throttles count against the total throttles
} else {
not throttled
}
So I bet you're seeing this behavior because the client accesses
between
access #1 and access #2 are too quick. I'm thinking it would be nice
if
you could see what type of throttle was triggered:
cfthrottle.type = "normal"
cfthrottle.type = "quick"
Because you might want to not fail on quick throttles so easily.
----------------------------------------
> You realize you could easily do your own throttle implementation using a
> CFC --- there is nothing really magically going on under the covers.
>
> It was based off the mod_throttle apache module a __long__ time ago, and
> it was pretty much a java port of that logic. So chances are, it may
> need revisiting.
Yes, I just thought this might be an easy way to deal with people
trying to download the whole site, but doesn't seem to really do
anything if simply resetting and they continue on.
Plus I can't figure out the hit logic anyway, as explained. With
default 500 minhittime why someone is throttled with only 6 total hits
(well below my requirement) makes no sense.
Maybe the tag should be deprecated?
Thanks.
--
Open BlueDragon Public Mailing List
http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon
mailing list - http://groups.google.com/group/openbd?hl=en
!! save a network - please trim replies before posting !!
