Movie files & .htaccess
 

Hiya,

I just wonder what problems I might encounter when I try to protet movie files in a webdirectory that's been secured with .htaccess.
Could some site-leecher programs evade this .htaccess protection?

yes

you know of any way to secure those files?

One of the Like Whoa techs wrote a custom-script for my server that does a kick-ass job of protecting avi files. It works like a charm.

Read the rules and clean up your signature please..

But, to answer your question, you cannot protect moviefiles using htaccess because most movie viewers don't send referrers.

You could conseal it in an html file, protect that file with htaccess, and have the name of the movie files changed every 10 mins.

What's no ok with my sig?

Q: I want to create a signature what guidelines should I follow when doing so?
A: a 120x60 button is cool. And up to 3 lines of text.

I got a button 120x39 and I only use 2 lines of text... I just would like to know what's not good.


Btw, thanks for all that input.

Eru: You're not gonna hand you that custom script I suppose?

Your 2 lines show as 4 lines in my browser.. :)

Mine too. Take out the quote, no one cares.

Ask your host to install movie file protection
.htaccess will not work

The script I use is more effective for the hotlinker can still see the movie. So when he adds the direct links to the movie in his BBS, all of his surfers will get sent to my sponsor. It's free traffic!

WSJB (whatever the fuck your name is): No, I can't give the script out.

The only way to use .htaccess to block hotlinking is with a cookie script. The only drawback is surfers that dont have cookies enabled will not be able to watch/download the video file. Works fine otherwise.

Ever heard of doing a GFY search ?

Regarding Sig: Well, it really shows me only two lines of sig...

Regarding Search: I did do a search but there was only hotlinking covered to some extent. I'm not sure if that also works for site-leeching programs and stuff and what else there might be involved....

Working solution: having the directory renamed every once in a while with a cron job but wouldn't that put an extensive load onto the server? My unix knowledge is not that vast and I don't know how much cpu and other ressources the renaming of a movie directory uses... so I was trying to find some alternate ways of protecting them.

Unplug your computer. :)

There's a thread on .htaccess on this board, search for it, I think it explains quite a lot, but I can't remember any of it. ;)

i guess, what you are talking about is ***having your movies in a member area protected by .htaccess/.htpasswd combos*** and now you want to make sure, no one of your members can download all the movies at once with a ***Leech*** program..., right???

***Regarding dynamic dirs***: this won't help shit for this purpuse, just will make it harder to find your movie files...

I've encountered the same problem. I found out that AVI's can be protected by .htaccess. Now I convert all my movies from mpg to avi and it's all good....

have something like this in your .htaccess...

1.)

RewriteCond %{HTTP_USER_AGENT} ^.*Crawler.*$ [OR]
RewriteCond %{HTTP_USER_AGENT} ^.*Snagger.*$ [OR]
RewriteCond %{HTTP_USER_AGENT} ^.*Teleport.*$ [OR]
RewriteCond %{HTTP_USER_AGENT} ^.*Reaper.*$ [OR]
RewriteCond %{HTTP_USER_AGENT} ^.*Wget.*$ [OR]
RewriteCond %{HTTP_USER_AGENT} ^.*Grabber.*$ [OR]
RewriteCond %{HTTP_USER_AGENT} ^.*Sucker.*$ [OR]
RewriteCond %{HTTP_USER_AGENT} ^.*Downloader.*$ [OR]
RewriteCond %{HTTP_USER_AGENT} ^.*Siphon.*$ [OR]
RewriteCond %{HTTP_USER_AGENT} ^.*Collector.*$ [OR]
RewriteCond %{HTTP_USER_AGENT} ^.*Mag-Net.*$
RewriteRule /* http://www.noscripts.com/ [L,R]

(list not complete)


2.)

change the name of your member dirs dynamically


3.)

use session management and update your .htaccess every 10 min, delete expired sessions out of the .htpasswd...