Select to view content in your preferred language

Strange Crossdomain.xml policy issue.  Channel.Security.Error

2459
2
Jump to solution
08-28-2013 07:23 AM
Scott_Russell
Regular Contributor
I have two applications created with AppBuilder that are running fine, and have been running well for the past year.  I just upgraded the AppBuilder to 3.4, the newest release.  Before upgrading my applications I wanted to create a new application.  Well, after creating the application I copied the crossdomain.xml file out of the existing applications in the wwwroot/flexviewers location and I'm receiving a crossdomain policy error:

"Basemap layer failed to load: Fault code: Channel.Security.Error

Fault info: Security error accessing url

Fault details: Destination: DefaultHTTP"



This is what is contained in our crossdomain policy, keep in mind that it works successfully for our existing application, but not for any new applications that I launch with AppBuilder:

<?xml version="1.0" ?>
<cross-domain-policy>
<allow-access-from domain="*" secure="false" />
<site-control permitted-cross-domain-policies="all" />
<allow-http-request-headers-from domain="*" headers="*" secure="false" />
</cross-domain-policy>


We've tried different variations of this, such as removing the 'secure="false"' tag. 

I believe this may be associated with the upgrade of AppBuilder in some way.  I'm at a loss for solutions at this point.

I also have another problem, in which coded domains will be included with web services sometimes, and sometimes not.  I cannot determine what the catalyst is in this case.  If anyone could point me to any literature at all relating to this subject, it would be very much appreciated.  I have spent countless hours on google trying to find any information at all for it.

We recently installed SP1 for ArcGIS Server and also the Web Adapter.

Thanks,
Scott
Tags (2)
0 Kudos
1 Solution

Accepted Solutions
AnthonyGiles
Honored Contributor
Scott,

For your new applications that are not working can you check the main configuration file (config.xml) and make sure that your server names for your base and operational layers are correct and its not trying to use something like localhost.

Regards

Anthony

View solution in original post

0 Kudos
2 Replies
AnthonyGiles
Honored Contributor
Scott,

For your new applications that are not working can you check the main configuration file (config.xml) and make sure that your server names for your base and operational layers are correct and its not trying to use something like localhost.

Regards

Anthony
0 Kudos
Scott_Russell
Regular Contributor
Scott,

For your new applications that are not working can you check the main configuration file (config.xml) and make sure that your server names for your base and operational layers are correct and its not trying to use something like localhost.

Regards

Anthony


Anythony thank you so much for replying in such a timely manner.  I recently changed the geometry service location in the AppBuilder settings to reference our ArcGIS Server rather than the ESRI service.  Now that I look through the config.xml I see that localhost exists here.   I never thought this could be the problem, I VERY MUCH appreciate your help.  PHEW!!

Thanks,
Scott
0 Kudos