[learnalist]

Would anyone care to put forward a solution to proactively tackle a similar script.

What I am specifically after, methods to know that this one computer ( keep it simple ) has sent x 1,000 requests in a short time ( ie to quick to be human ).

Before some of you lay the blame purely on AT&T for having poor code.

Other scenarios which are similar but different.

Perhaps we want to use this to throttle api requests, or to tackle a brute force attempt on the login.

[learnalist]

To aid in my own discovery. http://news.ycombinator.com/item?id=1123172

A little more info, but not alot. More monitoring.

Equally discovered PHPIDS, reading how it works. Im not sure this would have picked up on this attack vector, as it would have been legitimate traffic. Just rapidly used.