Forum Moderators: open
Or you can make this a server side process of a critical page often accessed, then when someone hits between the hours of 4am and 5am, the renaming happens, and once it is done, it is not done again until next day.
Then modify your pages that the image names are dynamically generated, either at server side, or as JavaScript to match the above schema.
Replace the image with something BIG that explains what bandwidth theft is and telling everyone to send an email to their ISP - and give the ISP email address.
Replace the image with some really guesome bloody pictures.
replace the image with a 1X1 gif (to reduce your bandwidth)
Rename the images.
Rename the directories.
Block based upon referrer.
Report them to their ISP.
Richard Lowe
[edited by: engine at 1:09 pm (utc) on Mar. 29, 2006]
[edit reason] TOS [/edit]
If that doesn't work, perhaps the logo for some ultra-Christian or ultra-feminist organization might be more fun
Tom
sorry, can't remember who had used it
That was me, but I'm certainly not the originator of the idea. It's too bad that most webmasters will include height/width attributes, but if they don't, you can really have some fun. I'm sure they loved seeing the pirate flags spread across their page, with their content shoved off the right hand side...
If I saw that someone was in fact linking to a song, I would swap the file for an audio (.WAV) file of the Meg Ryan coffee shop scene from When Harry Met Sally.
In your raw logs it will be obvious since the referrer will only get a file and not a page. Likewise, if you are using analog or another webstats analyzer, the referrer will not request a page, but only the file(s).
Here's some free anti-leeching scripts [hotscripts.com]
Another way to stop images from being remotely linked, is to add this to the .htaccess file in your images directory:
RewriteCond %{HTTP_REFERER}!^http://yoursite.com/ [NC]
RewriteCond %{HTTP_REFERER}!^http://www.yoursite.com/ [NC]
RewriteRule [^/]+.(gif¦jpg)$ - [F]
I am using webalizer and the history feature, then deleting the logs daily at 4am by cron, have to or it would devour the server like a fine steak with A1 sauce.
I can see all my refferers, but it doesnt say exactly what the refferers are getting...
Kinda hard to tell if its happening or not but I suspect it (paranoid by nature).