Quote:
Originally posted by RedShoe
gees louise. I'm kidding.
And no I didn't see the whole thing I just saw a kid and an elephant and once I saw the CJ watermark, I just assumed it'd be a snuff film.
If you are serious about the hotlinking thing go to microsoft's site they have some BAD ASS anti hotlink type shit there, it some how ONLY let's members download your shit. It's hardcore. go to ms and look around.
|
Ok Red, sorry been a long night.....
I would never post a snuff film!
I kinda thought it was funny...
Protecting media files in a members area is easy... it the exsposed one that are hard cause there is no REF URL sent by the players.... there is basically no info to help in the GET request.
Here is a sample GET request from Windows Media Player...
GET /justblow.asx HTTP/1.1
Accept: */*
User-Agent: Windows-Media-Player/9.00.00.3075
Accept-Encoding: gzip, deflate
Host: 64.69.89.155:8080
Connection: Keep-Alive
It does not tell you anything......
.htaccess also relies on REF URL to protect stuff as well....
No problem for browsers.... but a major pain for the media players..
Hence the problem...
When I worked for Lens..... we delt with the same thing...
I wrote an NT servce..... that....
1) at set intervals, stops the required services
2) renames the directory
3) updates the databsae that script pages call for directory name
4) restart the services
But proved to to be buggy and unreliable.... Windows does not
like to give up its locks on files all the time.
Seems that a lot of other people have taken the same approach and have found the same thing...
Im trying something here that take a completly different approach... just try to see if its crackable....
I could not hotlink it... but Im not privy to all manner of hotlinking....
