I missed the point of it being a matter of overhead. Sorry about that. I guess I fumed this thread up enough.
"Apache's mod_dosevasive," I'll look into that.
The point you folks are making is that at this time it's not practical to have UBB do any of this (understood and the answer is honest and fair) and even it was there was, other improvements with greater benefits overall are in the works
The operative point is all CGI can make a server vulnerable, and if that’s the case and if anyone is the unlucky owner of a targeted server, then finding a better means of protecting the server overall is where the focus should be, and not on the individual programs.
I realize that I have been unfair here, it just so happens that this time it was UBB so where better to cast the blame. It’s really the jerks that perpetrate these things that should be feeling the heat, not you guys.
The important point is it’s not UBB Classic's problem, it’s my problem, and I need to find a way to isolate things like this when they happen more effectively and not blame the CGI programmers.
I can be a cranky chap, but I do appreciate you guys taking the time to set me straight. Thank you all for helping me through the aggravation.
