Forum Moderators: open
But now I had a ripper that didn't only request several different files within the same second, it requested each file six times simultaneously. As soon as one of the six downleads finished, the other five in progress were aborted, resulting in one thousand 206's. Such ripping could use up a site's monthly bandwidth in an hour, like a DOS.
A simply solution could be to direct all clicks (right AND left) on wav links to a separate html page with a "Start download" button. Ordinary visitors can click the button, but most rippers probably wouldn't bother to write a circumventing code. The button script should remember the original URL of the link and hopefully require as little modification to the original html page as possible. Is there such a thing?
Blocking by IP after x downloads in y seconds could be another solution, it's an Apache server (virtual hosting), but how to automate that? It's useless to try blocking by UA as it is forged. Throttling isn't an option - the ripper will just use up the same bandwidth in 5 hours instead of 5 minutes.