brute force http request floods replicate legitimate http headers and get/post requests and make literally thousands upon thousands of requests GET and POST sends/requests over the internet. The smart attacker will use a list of anonymous proxy servers, holding the connection until it is dropped, and use smart cookie management.
This can slow down and possibly freeze a web server/DB server if there isn't bandwith/load management high enough to compensate for the load or security scripts in place checking for said, or limiting the potential for it.
This can be a tedious affair for any web server admin whos' server /script is targeted and doesnt have a defense mechanism(s) built in for this. He/she usually has to manually reads the logs and manually bans the proxy ip's, unless they have a flood protection script that automatically bans flooding ips.
And if they are range banned you are limiting legitimate users.
Most decent content management systems have script protection in place for the inputs, limiting the potential and damage it can cause.
There is a web server/script stress testing tool available at http://cafecounterintelligence.com to test any script or webserver you own, but be very careful lol ... it is called JackHammer ... there is also a drop-in, configurable php script that helps to protect against this form of attack there as well, called CCISecurity, and anotehr for configuring downlaods with CCISecurity, called Filepipe.php