Skip to main content
O
olafnew
Participating Frequently
March 20, 2012
Question

RTMP allowedSWFdomains problem with firefox

  • March 20, 2012
  • 2 replies
  • 1379 views

I have an RTMP application(LIVE). Using included security measures - i have provided a list of allowed domains in allowedHTMLdomains and allowedSWFdomains files. After that - all the RTMP live broadcasts - that hae previously worked at firefox - stopped working in firefox. why? And how do i fix that?

    This topic has been closed for replies.

    2 replies

    A
    Anonymous
    March 21, 2012

    The issue is caused by Flash Player 11.1.102.62 (released on February 15th, 2012) on Firefox for Mac and PC

    The issue has been adressed in Flash Player 11.1.102.63 (released on 4th of March 2012)

    I've documented the issue in this blog post: http://avchathq.com/blog/connection-rejected-you-did-not-connect-comming-from-a-licensed-domain-and-the-latest-flash-player-update/

    O
    olafnewAuthor
    Participating Frequently
    March 20, 2012

    Almost identical problem is discussed here: http://www.longtailvideo.com/support/forums/jw-player/servers-and-streaming/25128/firefox-with-flash-11110262-problem-with-rtmp

    O
    olafnewAuthor
    Participating Frequently
    March 20, 2012

    The working solution can be found here: https://bugbase.adobe.com/index.cfm?event=bug&id=3117684

    In two words - it's a bug. It can be fixed by doing the following:

    Assuming your secured applications are clones of VOD with a set of restrictions in allowedHTMLdomains.txt, you can edit \rootinstall\samples\applications\vod\main.asc thusly:

    Find the line domainEndPos = url.indexOf("/", domainStartPos);

    add this block after that line:

    // This patches the Firefox Bug

    if (domainEndPos == -1)

    {

    domainEndPos = url.length;

    }

    Then copy that main.asc file into the directory for your secure application and rename main.far something else ("main.far.backup"). When you restart the application, you won't see this problem again.

    O
    olafnewAuthor
    Participating Frequently
    March 20, 2012

    The fix i've mentioned earlier is FLAWED! It works incorrectly! It does fix the problem with Firefox, but it also breaks all logs(logs start to work improperly in an application where the fix was applied), but even more - it simply discards all settings set in allowedSWFdomains & allowedHTTPdomains!!! DO NOT USE IT. Just because of this unworkable fix somebody have streamed an illegal event through one of our servers!

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