Select to view content in your preferred language

SecurityError: Error #2048: Security sandbox violation for ArcGIS Online map services

2954
13
08-20-2010 12:08 PM
AlisonSengupta
Occasional Contributor
I am using the Sample Flex Viewer with IE 8 and every once in awhile I will get the following error.
SecurityError: Error #2048: Security sandbox violation: http://mydomain/myflexapp/index.swf cannot load data from http://server.arcgisonline.com/ArcGIS/rest/services/ESRI_StreetMap_World_2D/MapServer?f=json.

This doesn't happen all of the time.  I am not sure why it occurs especially with Esri's map services.  When it does happen I either have to wait awhile and try again or open a firefox brower and the data comes in just fine.  After that I can open an IE browser and it is working again.  Does anyone have any ideas what may be causing this?  It is driving me nuts.

Many thanks,
Alison
Tags (2)
0 Kudos
13 Replies
BjornSvensson
Esri Regular Contributor
Alison, you might want to work this through directly with Esri Support - http://support.esri.com/en/

All the responses from arcgisonline should come back as http/1.1.  I would try to figure out why some are coming back (or seem to be coming back) as http/1.0.  It doesn't sound like a browser cache issue (which is other times a usual culprit).  The firewall could indeed be playing a role.
0 Kudos
AlisonSengupta
Occasional Contributor
Thanks Bjorn.  I will log it in, and once the problem is resolved (hopefully it can be resolved) I will post it on the forum.  We have had a variety of outside users test our website without any problems.  So, this is definitely an internal issue.
-Alison
0 Kudos
CurtisBradley
Emerging Contributor
I would make sure the crossdomain.xml file is configured correctly.  I had these same errors (but not using a Proxy) until i downloaded httpfox to troubleshoot where the trouble was.  I basically copied Adobes crossdomain file pasted below just to get it to work and then tweaked it to make it more restrictive:

<?xml version="1.0"?>

<cross-domain-policy>
<allow-access-from domain="*" secure="false"/>
</cross-domain-policy>
0 Kudos
ChrisDougherty
Occasional Contributor
Allison,

I am experiencing a similar issue within my AIR app. Did you ever resolve the problem?
0 Kudos