Skip navigation
Currently Being Moderated

Problem with Firefox 10.0.2, Flash Player and allowedHTMLdomains.txt

Mar 1, 2012 6:49 AM

Hi all,


I have a Flash Media Streaming Server 4.0 running for more than a year now.

I protect the access to my server through the "allowedHTMLdomains.txt and allowedSWFdomains.txt feature"  (amongst other things...).

We noticed that with Firefox 10.0.2 (last version) and Flash Player (last version) our customers can't connect anymore.


In the admin console we can read things like :

     Authentication failed for pageurl:, rejecting connection from XXX.XXXXXX.XXX


If i try from the same computer with another browser, i get

  Accepted a connection from IP:XXX.XXX.XXX.XXX, referrer:, pageurl:


In the logs i have lines like that :


     --> connection error :


connectsession2012-03-0112:51:17CETXXX.XXX.XXX.XXXXXX.XXX.XXX.XXX6629219_defaultRoot__defaultVHost_vod_definst_0401XXX.XXX.XXX.XXXrtmpte(HTTP-1.1)2rtmpte:// 11,1,102,62470211256606584049530733106normal--------------------------




     --> connection successful:



WIN 11,1,102,62470211366552713662430733073normal--------------------------



I can't find any significant difference...



I didn't change anything in my configuration since the beginning, and the application was working without probleme with every version of Browser/FlashPlayer untill now.

I suppose this is a bug, from Firefox or FlashPLayer or FlashMediaServer.


Is there anyone from Adobe that could help me to solve this or "workaround" this, knowing that i must use the security features.


Thank you very much for your help!



  • Currently Being Moderated
    Mar 1, 2012 7:54 AM   in reply to samZas

    It's a known bug. The latest version of FP is truncating referrers on Firefox. See here:


    Mark as:
  • Currently Being Moderated
    Mar 1, 2012 8:18 AM   in reply to samZas

    No, I couldn't begin to guess on the timeline for flashplayer bugfixes, but obviously, it won't happen until at least the next flashplayer update.


    In the meantime, you should be able to work around it by limiting your allowedDomains to just domains, and not paths to pages or directories

    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points