Htaccess and video

You can't use .htaccess to protect media files from being hotlinked anyways, so don't even bother. There are some people on GFY that sell software to suit your needs. I'll post the link as soon as i can find it.

I'd love that link too!

I'am using Hotlinkprotector

http://www.hotlinkprotector.com


Pretty much identical to the other scripts, just way cheaper

Thanks. I'd appreciate a link to some software that I could look at for this.

see sig =)

This is included with all of our virtual plans at no cost.

http://www.xxxwebhosting.com/unixstreaming.htm

I've never had any problems with any of my vids being hotlinked thanks to mod re-write.

IS there some way a person(s) can avoid that .htaccess file and download? If so, how do they defeat the .htaccess file? (other than using someone's id/pw)

We had people bypassing the mod re-write using programs like

http://www.amazesoft.com/

The solution we do now is locked tight, no problems since.

Here you go, and 20% for me. Bwahahaha.

http://www.antihotlinking.com/in/choda

Thanks for the info. I will check out this software and see what it does. From what I read, it seems that these "mirror urls" pose a bigger threat than the actual software (though I see that this software enables that too!).

Anyone ever investigate http://www.shareurl.com to see what exactly they are all about?

You can´s protect movies with htacess using "allow-access-based-on-refering-domain" in the same way you can with a htacess that allows access based on htpasswd file.


The reason for the problem is that movie players use java and java does not send headers, therefore the calls are not identified as originating on your server.

However, you can use this:
Your htaccess should read:


RewriteCond %{HTTP_REFERER} !^http://([a-z0-9-]+\.)*your-domain.com/ [NC]
RewriteCond %{HTTP_COOKIE} !(^|(.+ *)id=valid(;.*|$)
RewriteRule /* http://%{HTTP_HOST}/ [R,L]

That last line redirects to your main index page... you can change it to something else if you want. The key line is where your server will check for the existence of a cookie. That isn't dependent on java, so it works.

You put the cookie code within the HEAD section of the first HTML document within your protected area:

hahahahahahahaha LANGUAGE="hahahahahahahahahaha">
// Calculate the expiration date
var expires = new Date ();
expires.setTime(expires.getTime() + 6 * 60 * 60 * 1000);
documenthahahahahahahaha = "id=valid; path=/" + "; expires=" + expires.toGMTString();
</hahahahahahahaha
That code expires the cookie in 6 hours. Adapt the 6 * 60 part to be whatever you want.

That should work, hope you can use it

OK, the code above doesn´t show right.
Email me and I´ll mail the correct code back to you