Limiting Duplicate HTTP GETs

Hi Ryan,

 

 

I think Deb's rule, RateLimit_HTTPRequest, is a little more straightforward for your scenario. The other rule has more functionality but is more complicated than what I think you need.

 

 

Are there specific URIs and/or client IP address ranges that you want to rate limit GETs for?

 

 

What do you want to do if a client makes multiple GET requests without the session identifying cookie?

 

 

Are the clients potentially malicious, or just badly configured/implemented? ie, will they potentially modify or delete their cookies?

 

 

When the flood of requests comes, is it from many different clients at the same time? To many different URIs?

 

 

Also, which LTM version (b version | head) and platform (b platform | head) are you using?

 

 

Thanks,

 

Aaron