FlashApe

FlashApe » Security Restrictions in the Authoring environment

Security Restrictions in the Authoring environment

September 14th, 2004
1:40 pm

Why?

While working on a project today, I was loading in some data via flash remoting from a remote server. thats fine, everythign works smoothly. Try to load in a jpg from the remote server, I get:

bq. *** Security Sandbox Violation ***
SecurityDomain ‘http://www.myserver.com/images/1.jpg’ tried to access incompatible context ‘file:///C|/wamp/www/website/myfile.swf’

Yeah baby!! Flash security restrictions in the authoring environment. God, I feel so secure.

The solution? Set allowDomain of the security object to the domain you want to load the swf/jpg from:

bc[as]. System.security.allowDomain(”http://www.myserver.com”);

Its a small little step, I know, but it’s one little step I’d like to not deal with while im developing, that I am just going to have to take time out and remove later.

123 CCTV Security Camera Surveillance Equipment - Security Systems Complete security camera systems and packages for the home or business.

flash

19 People had this to say...

I have an issue duplicating a loaded movie clip. DuplicateMovieClip emits the following error:

*** Security Sandbox Violation ***
SecurityDomain ‘http://testserver/assets/DeadTrees.swf’ tried to access incompatible context ‘file:////testserver/Inetpub/wwwroot/art/walkingdemo.swf’

note I use this: System.security.allowDomain(”http://testserver”);

The movie ends up not being duplicated.
Anyone have an idea?

thx for the security tip. i had exactly the same problem.

patrick heusser

cheers,
I had the same thing.

Me too, thanks

Thanks, thanks, thanks! You rule :bow:

It doesn’t work for me… I hate you all flash

you’re right, thanks

This problem most often happens when you are launching .swf file at, say, http://www.yoursite.com and loading SWF from http://yoursite.com/ (without WWW) and vice versa.
Just check paths attentively and use one path convention for all paths in your code. I am unsure whether everything else helps 100% with *** Security sandbox violation *** and incompatible context.

This has been bothering me for days. Thanks a lot!

Thanks You So Much!!!

thanks
you saved my day

Thank you soo much rich !

Even better, save some duplication and use this!

System.security.allowDomain(’*');

I was having the same problem trying to run an app in the flash environment loading and downloading JPGs off the server I am working on, and used the fix listed above, but upon some mouse events that I was using to enable drag/drop functionality, the same security sandbox error would still happen - very annoying.

The fix I found was to use ANOTHER container movie clip inside the original to load the remote image, and then applying all property changes, mouse events, or other interactive manipulations of the object to the outermost container movie clip, and not the inner one holding the image. For whatever reason, I guess this separates the cross-domain loaded object from the events, even though the outcome is the same.

In this manner, I didn’t even need the System.security.allowDomain(’*'); fix, although that did clear up a number of the errors initially.

So, try creating an innerHolder type workaround if you can’t seem to get rid of those annoying Sandbox errors..

thanks alot, it solved my problem!

@Sean Powell

yep that solved my **SandBox** problem too ..

You are a genius

…im back in “Hello actionScript World”

[…] Security Sandbox Violation AFAIK, it’s to do with cross domains - see fix HTH __________________ CSS Trickery | CSS Tutorials, Tips and Tricks for all […]

Hah, thanks for the post.

I have been doing ActionScript 3 for quite some time now, and was getting really really angry that Security.allowDomain(”*”) was not working in this ActionScript 2 project I am working on.

Your nice post kicked me right back into ActionScript 2 mode.

I couldn’t get it to work I still get the stupid security message:

Do I need to change anything in this? I just copied and pasted the exact code??

bc[as]. System.security.allowDomain(”http://www.myserver.com”);

Security Restrictions in the Authoring environment

19 People had this to say...

Want your say?

Contact

Search this site

Gullible

Links

Categories

Archives