Quote:
Originally posted by quiet
if your talking pure logistics, this is not the type of img src i'm talking about. what i'm envisioning is someone with millions of daily unique visitors, going after someone with under 100,000.
|
reversing the attack isn't the only option... it is also possible to deny via htaccess, and send the 403 traffic to another site. for example, elephant list was img src'ing a while back, the 'victim' redirected the attack to gfy, and brought it down.
they don't have to reverse the attack to where it came from... it can be sent to fbi.gov and the attacker's url will show as a referrer, the 'victim' url won't. that could be nasty. ;-)
it doesn't really matter if a site can handle 300% of the traffic they are getting now... they can reverse to a movie file that may be 1 or 2 megs in size, although the setup could handle it with ease, it will $ cost the img src'er. :-)