So complete path to the clip will be
5.stream contains this:
So wowza reads content of the file and recieves stream described there. But what if we will tell wowza not just a file name from
content directory, but complete http url to some destination which also contains just rtsp-path (just text), it could be even the same 5.stream file - this will give us great opportunity to completely hide real video source from user (security reason and requirement in my project). Particulary, such url will be a path to some php/jsp/what_ever page which will send back text rtsp-path after making some logic (user authorization/session vars/user cookies), for example it will be
I think the best course of action here would be to modify the player such that it does this http query prior to stream resolution. This way the player would get the stream url internally and then play it back. For JWPlayer, you could try
utilizing their existing api. However, in doing this, you won't be really adding much more security other than a thin layer of obfuscation.