AllowedSWFdomains.txt and allowedHTMLdomains.txt files

Question

We're trying to take a different tack in resolving our issue with offsite streams coming through our server.
in the /rootinstall/Applications/vod and live folders, there are two text files which when altered, purportedly should only allow flash within html pages, and swf files to only be allowed if they reside on computers on specified domains. (Files are mentioned here)
Am I understanding those files correctly?   I ask, because when I set them all by removing the asterisk from the last line, and repacing it with our domain.edu , i thought that meant that the server should only respond to swfs and htmls located on our domain computers....
In a simple test from home, I fired up an swf that I know calls an mp4 from our server.  It played.   If I understand things correctly, it shouldn't have.
are the other switches to be thrown to make these files do what I believe their supposed to?  or is this not their purpose?
Also... is that the only place they need to exist?  or is it something you have to throw into every flash app folder on the server

Answer 1

I think we found a suitable solution to our problem.  We edited main.asc to add an if/then block to set write access to the server.
    if(p_client.ip == '{our IP Address}'){
        trace('We are all good: ' + p_client.writeAccess);
    else{
        p_client.writeAccess = "";
So if they come from anywhere other then our IP, they can't publish.  This doesn't reject the connection however, so they can still send stuff too our server...but it just doesn't go anywhere.  If we could detect what they were trying to do before we accepted the connection, we would be able to reject the connect outright.  Although, I haven't figured that out yet.
People should be able to modify that to block out ranges or domains as well.  I made this change in the application.onConnect = function( p_client, p_autoSenseBW ) function call.
I will note however, that much hair was pulled until we realized that main.far overrode main.asc.  Once we renamed main.far to main.farther, our main.asc code started working, and we were able to block.  Just an fyi to save you time if you go this route.  If you are doing more then simply streaming from your FMIS server (and most of you probably are) this is probably not a great solution.