Forum General Static VS Connected gameFS, HTTPS Sandbox issue

Any issues or discussions relating to Flash development are welcome here.

Static VS Connected gameFS, HTTPS Sandbox issue

Postby arnoldsgn » May 23rd, 2013, 8:16 pm

Having flash security issues with the "connected" form of gameFS, but not the "static" one.
The static one is accessed like this: PlayerIO.gameFS(GAME_ID)
and the connected one is accessed like this: function playerioConnected(client:Client):void{ gameFS=client.gameFS;}

I want to use the connected version of gameFS, because the static one is slower and does two url calls for each asset -one that starts with a "r." in the url, which gets forwarded to an Akamai location.

The connected one is faster-HOWEVER- it creates a Security Sandbox violation when swfs load swfs over https, because the domain from sitebox's "{% swf" directive is, but the domain of the [connected] game fs url being loaded is

I've implemented some security related code to help, but these do not fix the issue:

context.securityDomain = SecurityDomain.currentDomain;
context.allowCodeImport = true;

Anyone know a fix for this ?
Posts: 1
Joined: May 24th, 2012, 9:30 pm

Return to General