Need Help...Desperatley

....Really Need Help

[Avoided Destiny]

Hello, I'm a newbie here.

Anyways...I run a site with MP3's on them. Well, another site has hot-linked multiple....and well, it's absolutely killing my bandwidth like no other and costing me money

I uh, desperatley need a way to block it. Images are one thing but MP3 blocking is new to me.

Any help is appreciated.

[jdMorgan]

Avoided Destiny,

Welcome to WebmasterWorld!

We've gone over this subject quite a bit recently. Here's a search [google.com] that will turn up some answers for you.

Jim

[Avoided Destiny]

Thanks, but it didn't help that much.

Here's the low down: My site has a ton of mp3's. However, another site is using <embed src=www.mydomain.com/mymp3s> or whatver it is. So, they get back ground music of my site, costing me bandwidth and money.

I, uh, need it to stop...badly. I just need a coding for it.

[Another site I know of protects] their midi's. When you click it....it bring you to a page they made. Making the page I can do, but if I can have it similar to their's or just completely stopped, it would be appreactiated...greatly

[edited by: jdMorgan at 4:51 pm (utc) on Mar. 25, 2005]
[edit reason] Removed specifics per TOS. [/edit]

[Avoided Destiny]

Sorry for the double....but there's no way to stop other sites embedding mp3's?

[jdMorgan]

> I, uh, need it to stop...badly. I just need a coding for it.

The search link I posted leads to a number of threads, in which the following are discussed:

• Simple HTTP_Referer-based "anti-hotlinking" methods will fail, because media players invoked by "embed" and "object" methods do not provide an HTTP_REFERER. Therefore it is impossible to determine what site the link to the media file came from. (HTTP_Referers are unreliable anyway; They can be removed, spoofed, or simply not present for many legitimate reasons).

• One more-robust solution uses a cookies-based method, where your page(s) on your site(s) set a short-term cookie. Next you arrange that all image requests to your site(s) are passed to a script that checks the cookie. If the cookie is present and valid, then the script serves the image. If not, you can reject the request and either provide alternate content or just an error message.

• Another more-robust solution is to password-protect the content, and require a user login.

• Between the simple "anti-hotlinking" methods that won't work with audio/video files and the sophisticated cookie-script method, another relatively-simple method exists. That is to periodically change the names of your media files --either manually or automatically-- so as to break the links on other sites. Another member is currently working on a version of that method here [webmasterworld.com].
  

Jim

[Avoided Destiny]

Sorry....cause then I didn't see them.

Do you know which would be the best? And where the links are?