|Posted: 27 November 2005 at 9:39pm
I'd like to integrate hotlink blocking into my website without having to undo my existing protection.
The current scheme involves hiding the URL of the target file by reading it from a database, then opening a Windows ASX file which refers to the actual file. So when the user clicks on "view source", all he sees is "filename=wmv.asp?ID=1234". The asp file then renders itself as an asx file, pointing to the actual video file.
This system has been working for me without hotlink protection enabled. And with hotlink protection enabled, I can get the video to play when I link directly to it. It's only when I combine hotlink protection with the ASX redirect that the video breaks. Note that all files in question are located on a whitelisted server.
Is there a way to get these two technologies to work together, or am I forced to choose between the two?
Thanks in advance for your advice.