We has some proprietary audio files we are streaming via html5. These files sit in an Amazon S3 bucket.
The audio files have special high and low pass filters and other scientific alterations and were recorded by our own orchestra.
The files won't be available for direct download, but we are streaming them with html5 audio.
Any super user could easily watch the http requests, see what the audio file url is, punch that in their address bar, then download it. Which is against our terms of agreement which they agree to.
We want it so only our website can access the files and use them within our application.
I can see that you can allow by IP:
<Directory /var/www/> <Files filename.ext> Order allow,deny Allow from 192.168.1.1 </Files> </Directory>
But what about by domain name/server?
Would putting our server IP there do the trick? Local IP? I wouldn't think so since I am guessing that checks against the client's IP from the browser.
I understand anyone with the right sound card or software can record the files themselves while listening. Oh well, my goal isn't to make it impossible, its to make it harder.
So the question in a nutshell is, how do I make it so only our website can access the audio files and stream them to the user?