| RAS 230 2005-06-06, 6:07 pm |
| I switched webhosting companys not too long ago and I'm still sort of moving
in. checking over my logs I noticed alot of people hotlinking to some of my
files.
I hadn't seen that in a long while because I setup an .htaccess file
originally to prevent that sort of thing but hadn't uploaded it yet to the
new server.
I upload the file but it didn't seem to work as I had expected. it only took
a moment for me to realize where the problem was.
my old host had my site on a unix system running apache, and this new host
hs it is a microsoft system running iis.
I've been looking for something that will work the way the .htaccess used to.
previous posts here, and other websites in general sugested everything from
creating custom ISAPI filters, editing the web.config file, editing the
global.asax, installing commerical packages like HotLinkStop, requireing
active sessions, setting then checking for cookies, using randomly generated
file names on access, the list goes on and on, but even information I found
that went into any detail on these subjects included paragraphs of code, or
would require re-writing the simple html/css pages I have.
I'm all for having options but everything I've read about so far has me
longing for the 4-6 lines of short and sweet code I had in the old .htaccess
file.
I have one directory full of files that I'm looking to keep from being
hotlinked.
not images, but things like exe, zip, and wav files.
maybe it's all just too new to me still but any help with this would be
great.
|