Skip to main content
C
CarphuntinGod
Known Participant
February 10, 2010
Question

allowedSWFdomains.txt and allowedHTMLdomains.txt files

  • February 10, 2010
  • 2 replies
  • 1901 views

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

    This topic has been closed for replies.

    2 replies

    T
    T-Hawk__DELT_
    Participating Frequently
    February 10, 2010

    We modified the files in the same way and although we didn't test as you did, our reason for changing the file was different.  Someone was bouncing live streams off our server, and altering this file now rejects all of those bounces.  So it seems like it works for us, FMIS 3.5.3.

    However, we had a side effect where it blocked our encoder from connecting to the box.  So our vod stuff streams properly, our live stuff doesn't work at all any more.

    C
    CarphuntinGodAuthor
    Known Participant
    February 10, 2010

    Talking to someone else, on the live encoding side, I'm likely to restrict live encoders via ip, and then have our remote encoders vpn to our campus.  If the server honors the IP restriction, we should be good to go, and unauthorized incoming streams should be killed

    Janaki Lakshmikanthan
    Adobe Employee
    Janaki Lakshmikanthan
    Adobe Employee
    February 11, 2010

    You can restrict the clients based on the IP using C++ Authorization Plug-in. Pls refer the "plug-in dev" document that comes with the FMS installation.

    Regards,

    Janaki L

    C
    CarphuntinGodAuthor
    Known Participant
    February 10, 2010

    I'll jump in quick and say I misread, or didn't read the swf file closely enough.  I

    now see that it says it only applies if the swfs are called from a web page.  So I quick ran my test again... using an html that calls the swf.   Well, still wasn't stopped.

    dang it.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices